System and method for providing a self-monitoring, self-reporting, and self-repairing virtual asset configured for extrusion and intrusion detection and threat scoring in a cloud computing environment

ABSTRACT

A trigger event monitoring system is provided in one or more virtual assets. One or more trigger parameters, including security threat patterns, are defined and trigger data is generated. The one or more trigger monitoring systems are used to monitor extrusion and intrusion capabilities and self-monitored trigger events that may harm or otherwise leave a virtual asset in a vulnerable state. In one embodiment, trigger events and monitoring of at least a portion of message traffic sent to, or sent from, the one or more virtual assets are initiated and/or performed to detect any message including one or more of the one or more of the trigger parameters. Any message meeting the one or more trigger parameters is identified as a potential security threat and is assigned a threat score, which is provided to the virtual asset. Various corrective actions may take place.

RELATED APPLICATIONS

This application is a divisional of Lietz, et al., U.S. patentapplication Ser. No. 15/581,835 (INTU148121-CON2), filed on Apr. 28,2017, entitled “SYSTEM AND METHOD FOR PROVIDING A SELF-MONITORING,SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET CONFIGURED FOREXTRUSION AND INTRUSION DETECTION AND THREAT SCORING IN A CLOUDCOMPUTING ENVIRONMENT,” which is a continuation of Lietz, et al., U.S.patent application Ser. No. 14/256,289 (INTU148239), filed on Apr. 18,2014, entitled “METHOD AND SYSTEM FOR PROVIDING SELF-MONITORING,SELF-REPORTING, AND SELFREPAIRING VIRTUAL ASSETS IN A CLOUD COMPUTINGENVIRONMENT,” and is a continuation of Lietz, et al., U.S. patentapplication Ser. No. 15/067,528 (INTU148121-CON1), filed on Mar. 11,2016, now U.S. Pat. No. 9,686,301 entitled “METHOD AND SYSTEM FORVIRTUAL ASSET ASSISTED EXTRUSION AND INTRUSION DETECTION AND THREATSCORING IN A CLOUD COMPUTING ENVIRONMENT,” which is a continuation ofLietz, et al., U.S. patent application Ser. No. 14/171,438, filed Feb.3, 2014, now U.S. Pat. No. 9,325,726 entitled “METHOD AND SYSTEM FORVIRTUAL ASSET ASSISTED EXTRUSION AND INTRUSION DETECTION IN A CLOUDCOMPUTING ENVIRONMENT” and is also a continuation of U.S. patentapplication Ser. No. 14/292,700, filed May 30, 2014 now U.S. Pat. No.9,342,690 entitled “METHOD AND APPARATUS FOR A SCORING SERVICE FORSECURITY THREAT MANAGEMENT,” all of which are incorporated by referencein their entirety as if they were fully set forth herein.

BACKGROUND

As various forms of distributed computing, such as cloud computing, havecome to dominate the computing landscape, security has become abottleneck issue that currently prevents the complete migration ofvarious capabilities and systems associated with sensitive data, such asfinancial data, to cloud-based infrastructures, and/or otherdistributive computing models. This is because many owners and operatorsof data centers that provide access to data and other resources areextremely hesitant to allow their data and resources to be accessed,processed, and/or otherwise used, by virtual assets, such as virtualmachine and server instances, in the cloud.

In a cloud computing environment, various virtual assets, such as, butnot limited to, virtual machine instances, data stores, and variousservices, are created, launched, or instantiated, in the cloud for useby an “owner” of the virtual asset, herein also referred to as a user ofthe virtual asset.

Herein the terms “owner” and “user” of a virtual asset include, but arenot limited to, applications, systems, and sub-systems of softwareand/or hardware, as well as persons or entities associated with anaccount number, or other identity, through which the virtual asset ispurchased, approved, managed, used, and/or created.

Typically, a given cloud computing environment receives message trafficthrough one or more network communications channels. One long standingproblem associated with cloud computing environments is the fact thatmalware can be introduced into the cloud computing environment, just asin any computing environment, via these network communications channels.The introduction of malware into a virtual asset, and therefore into anapplication, service, enterprise, or cloud infrastructure of a cloudcomputing environment is known as intrusion. However, once introduced,some forms of malware take control of some, or all, of the infectedvirtual asset functionality and use the virtual asset to send outboundmessages and data. This outbound malware mechanism is referred to asextrusion.

The detection of both malware intrusion and extrusion is an importantpart of making cloud computing environments more secure. However, agiven cloud computing environment can include hundreds, thousands, oreven millions, of virtual machines and other assets, owned or used byhundreds, thousands, or even millions, of parties and, in many cases, agiven application or service can operate within, and interface with,multiple cloud computing environments. Consequently, detecting malwareintrusion and extrusion is an extremely difficult and resource intensivetask.

Further, with respect to cloud computing environments, one majorsecurity issue in a cloud computing environment is that vulnerabilitiesassociated with virtual assets are not always known or understood at thetime the virtual assets are created and deployed, e.g., instantiated, ina given computing environment and, once deployed, detecting and/orresponding to newly identified vulnerabilities through “normal”communications channels associated with the virtual assets can bechallenging, if not impossible.

In addition, in some cases, a malicious entity is able to take controlof a virtual asset. In these cases, the malicious entity often takesover, or closes down, normal communications channels associated with thevirtual asset. Consequently, in some cases, the malicious entity canmask the fact they have taken control of the virtual asset from otherentities outside the virtual asset, such as entities deployed by theowner to monitor and enforce security policies. This leaves themalicious entity relatively free to manipulate the virtual asset underits control and access any data used by the virtual asset, with littleconcern of detection by the legitimate owner of the virtual asset. Evenin cases where the legitimate owner of the virtual asset does becomeaware that the virtual asset has been compromised, if the maliciousentity has shut down, or taken control of, the normal communicationschannels associated with the virtual asset, the malicious entity canthwart any traditional efforts by the legitimate owner to communicatewith the virtual asset and/or repair the virtual asset.

The situation described above represents a significant issue that mustbe resolved before highly sensitive data, such as financial data, can besafely processed in a cloud computing environment.

For reasons described above, what is needed is a method and system forproviding a virtual asset that can independently and automaticallydetect one or more trigger events within the virtual asset, generatesuspicious event reporting data from the virtual asset, and provide thereporting data to a monitoring system external to the virtual asset, allwithout relying on detection of the suspicious event by entities outsidethe virtual asset itself or the use of normal communications channels

Additionally, what is further needed is a method and system fordetecting and prioritizing malware intrusion and extrusion in cloudcomputing environments that makes use of existing cloud computingenvironment infrastructure, features, and assets.

SUMMARY

In accordance with one embodiment, a method and system for virtual assetassisted extrusion detection in a cloud computing environment includesprocess operations and system modules for self-monitoring andself-reporting virtual assets includes providing a virtual assetmonitoring system.

In one embodiment, one or more of the one or more virtual assets in acloud computing environment is provided a trigger monitoring system;thereby transforming the one or more virtual assets into extrusiondetection capable virtual assets. In one embodiment, one or more triggerparameters are defined and trigger data representing the triggerparameters is generated and provided to the trigger monitoring systemsof the extrusion detection capable virtual assets which are then used tomonitor at least a portion of the message traffic sent from the virtualassets in the cloud computing environment to detect any messageincluding one or more of the one or more trigger parameters. In oneembodiment, any detected message including one or more of the one ormore trigger parameters is identified as a suspect message.

In one embodiment, for each suspect message, a threat score is assignedto each suspect message at least partially based on a potential impactof the suspect message's potential security threats on the extrusiondetection capable virtual assets. In one embodiment, each threat scoreis provided to the extrusion detection capable virtual assets to enablethe extrusion detection capable assets to secure against the potentialsecurity threats.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram showing the interaction of variouselements for implementing one embodiment;

FIG. 2 is a functional block diagram showing the interaction of variouselements for implementing one embodiment;

FIG. 3 is a flow chart depicting a process for virtual asset assistedextrusion detection in a cloud computing environment in accordance withone embodiment;

FIG. 4 is a flow chart depicting a process for virtual asset assistedintrusion detection in a cloud computing environment in accordance withone embodiment.

FIG. 5 is a functional diagram of a virtual asset creation template inaccordance with one embodiment;

FIG. 6 is a flow chart depicting a process for providing self-monitoringand self-reporting virtual assets in accordance with one embodiment; and

FIG. 7 is a flow chart depicting a process for providingself-monitoring, self-reporting, and self-repairing virtual assets inaccordance with one embodiment.

Common reference numerals are used throughout the figures and thedetailed description to indicate like elements. One skilled in the artwill readily recognize that the above figures are examples and thatother architectures, modes of operation, orders of operation andelements/functions can be provided and implemented without departingfrom the characteristics and features of the invention, as set forth inthe claims.

DETAILED DESCRIPTION

Embodiments will now be discussed with reference to the accompanyingfigures, which depict one or more exemplary embodiments. Embodiments maybe implemented in many different forms and should not be construed aslimited to the embodiments set forth herein, shown in the figures,and/or described below. Rather, these exemplary embodiments are providedto allow a complete disclosure that conveys the principles of theinvention, as set forth in the claims, to those of skill in the art.

In accordance with one embodiment, methods and systems for virtual assetassisted extrusion, and/or intrusion, detection in a cloud computingenvironment include processes for virtual asset assisted extrusion,and/or intrusion, detection in a cloud computing environmentimplemented, at least in part, by one or more computing systems.

Herein, the term “production environment” includes the variouscomponents, or assets/virtual assets, used to deploy, implement, access,and use a given application as that application is intended to be used.In various embodiments, production environments include multiple virtualassets that are combined, communicatively coupled, virtually and/orphysically connected, and/or associated with one another, to provide theproduction environment implementing the application.

As specific illustrative examples, virtual assets making up a givenproduction environment can include, but are not limited to, one or morecomputing environments used to implement the application in theproduction environment such as a data center, a cloud computingenvironment, a dedicated hosting environment, and/or one or more othercomputing environments in which one or more virtual assets used by theapplication in the production environment are implemented; one or morecomputing systems or computing entities used to implement theapplication in the production environment; one or more supervisory orcontrol systems, such as hypervisors, or other monitoring and managementsystems, used to monitor and control virtual or other assets and/orcomponents of the production environment; one or more communicationschannels for sending and receiving data used to implement theapplication in the production environment; one or more access controlsystems for limiting access to various components of the productionenvironment, such as firewalls and gateways; one or more traffic and/orrouting systems used to direct, control, and/or buffer, data traffic tocomponents of the production environment, such as routers and switches;one or more communications endpoint proxy systems used to buffer,process, and/or direct data traffic, such as load balancers or buffers;one or more secure communication protocols and/or endpoints used toencrypt/decrypt data, such as Secure Sockets Layer (SSL) protocols, usedto implement the application in the production environment; one or moredatabases used to store data in the production environment; one or moreinternal or external services used to implement the application in theproduction environment; one or more backend systems, such as backendservers or other hardware used to process data and implement theapplication in the production environment; one or more software systemsused to implement the application in the production environment; and/orany other virtual or other assets/components making up an actualproduction environment in which an application is deployed, implemented,accessed, and run, e.g., operated, as discussed herein, and/or as knownin the art at the time of filing, and/or as developed after the time offiling.

As used herein, the terms “computing system,” “computing device,” and“computing entity,” include, but are not limited to, a virtual asset, aserver computing system; a workstation; a desktop computing system; amobile computing system, including, but not limited to, smart phones,portable devices, and/or devices worn or carried by a user; a databasesystem or storage cluster; a switching system; a router; any hardwaresystem; any communications systems; any form of proxy system; a gatewaysystem; a firewall system; a load balancing system; or any device,subsystem, or mechanism that includes components that can execute all,or part, of any one of the processes and/or operations as describedherein.

In addition, as used herein, the terms computing system and computingentity, can denote, but are not limited to, systems made up of multiple:virtual assets; server computing systems; workstations; desktopcomputing systems; mobile computing systems; database systems or storageclusters; switching systems; routers; hardware systems; communicationssystems; proxy systems; gateway systems; firewall systems; loadbalancing systems; or any devices that can be used to perform theprocesses and/or operations as described herein.

In various embodiments, the one or more computing systems implementingthe processes for virtual asset assisted extrusion, and/or intrusion,detection in a cloud computing environment are logically or physicallylocated, and/or associated with, two or more computing environments. Asused herein, the term “computing environment” includes, but is notlimited to, a logical or physical grouping of connected or networkedcomputing systems and/or virtual assets using the same infrastructureand systems such as, but not limited to, hardware systems, softwaresystems, and networking/communications systems. Typically, computingenvironments are either known environments, e.g., “trusted”environments, or unknown, e.g., “untrusted” environments. Typically,trusted computing environments are those where the virtual and/or otherassets and components, infrastructure, communication and networkingsystems, and security systems associated with the computing systemsmaking up the trusted computing environment, are either under thecontrol of, or known to, a party. In contrast, unknown, or untrustedcomputing environments are environments and systems where the virtualand/or other assets and components, infrastructure, communication andnetworking systems, and security systems implemented and associated withthe computing systems making up the untrusted computing environment, arenot under the control of, and/or are not known by, a party, and/or aredynamically configured with new elements capable of being added that areunknown to the party.

Examples of trusted computing environments include the virtual and/orother assets and components making up data centers associated with,and/or controlled by, a party and/or any computing systems, and/ornetworks of computing systems, associated with, known by, and/orcontrolled by, a party. Examples of untrusted computing environmentsinclude, but are not limited to, public networks, such as the Internet,various cloud-based computing environments, and various other forms ofdistributed computing systems.

In various embodiments, each computing environment includes allocatedassets and virtual assets associated with, and controlled or used tocreate, and/or deploy, and/or operate an application.

It is often the case that a party desires to transfer data to, and/orfrom, a first computing environment that is an untrusted computingenvironment, such as, but not limited to, a public cloud, a virtualprivate cloud, and a trusted computing environment, such as, but notlimited to, networks of computing systems in a data center controlledby, and/or associated with, the party. However, in other situations aparty may wish to transfer data between two trusted computingenvironments, and/or two untrusted computing environments.

In one embodiment, two or more assets, such as computing systems and/orvirtual assets, and/or two or more computing environments, are connectedby one or more communications channels including but not limited to,Secure Sockets Layer communications channels and various other securecommunications channels, and/or distributed computing system networks,such as, but not limited to: a public cloud; a private cloud; a virtualprivate network (VPN); a subnet; any general network, communicationsnetwork, or general network/communications network system; a combinationof different network types; a public network; a private network; asatellite network; a cable network; or any other network capable ofallowing communication between two or more assets, computing systems,and/or virtual assets, as discussed herein, and/or available or known atthe time of filing, and/or as developed after the time of filing.

As used herein, the term “network” includes, but is not limited to, anynetwork or network system such as, but not limited to, a peer-to-peernetwork, a hybrid peer-to-peer network, a Local Area Network (LAN), aWide Area Network (WAN), a public network, such as the Internet, aprivate network, a cellular network, any general network, communicationsnetwork, or general network/communications network system; a wirelessnetwork; a wired network; a wireless and wired combination network; asatellite network; a cable network; any combination of different networktypes; or any other system capable of allowing communication between twoor more assets, virtual assets, and/or computing systems, whetheravailable or known at the time of filing or as later developed.

FIG. 1 is a functional diagram of the interaction of various elementsassociated with one embodiment of the methods and systems for virtualasset assisted extrusion, and/or intrusion, detection in a cloudcomputing environment discussed herein. Of particular note, the variouselements in FIG. 1 are shown for illustrative purposes as beingassociated with specific computing environments, such as computingenvironment 10, computing environment 11, computing environment 12,computing environment 13, computing environment 14, and computingenvironment 15. However, the exemplary placement of the various elementswithin these environments and systems in FIG. 1 is made for illustrativepurposes only and, in various embodiments, any individual element shownin FIG. 1, or combination of elements shown in FIG. 1, can beimplemented and/or deployed on any of one or more various computingenvironments or systems, and/or architectural or infrastructure virtualand/or other assets and components, such as one or more hardwaresystems, one or more software systems, one or more data centers, more ormore clouds or cloud types, one or more third party servicecapabilities, or any other computing environments, architectural, and/orinfrastructure virtual and/or other assets and components as discussedherein, and/or as known in the art at the time of filing, and/or asdeveloped/made available after the time of filing.

In addition, the elements shown in FIG. 1, and/or the computingenvironments, systems and architectural and/or infrastructure virtualand/or other assets and components, deploying the elements shown in FIG.1, can be under the control of, or otherwise associated with, variousparties or entities, or multiple parties or entities, such as, but notlimited to, the owner of a data center, a party and/or entity providingall or a portion of a cloud-based computing environment, the owner or aprovider of a service, the owner or provider of one or more resources,and/or any other party and/or entity providing one or more functions,and/or any other party and/or entity as discussed herein, and/or asknown in the art at the time of filing, and/or as made known after thetime of filing.

In one embodiment, one or more cloud computing environments areprovided. In various embodiments, the one or more cloud computingenvironments are used to create, and/or deploy, and/or operate anapplication that can be any form of cloud computing environment, suchas, but not limited to, a public cloud; a private cloud; a virtualprivate network (VPN); a subnet; a Virtual Private Cloud (VPC); anysecurity/communications grouping; or any other cloud-basedinfrastructure, sub-structure, or architecture, as discussed herein,and/or as known in the art at the time of filing, and/or as developedafter the time of filing.

In many cases, a given application or service provided through a cloudcomputing infrastructure may utilize, and interface with, multiple cloudcomputing environments, including multiple VPCs, in the course ofproviding the associated service. As noted above, each cloud computingenvironment includes allocated virtual assets associated with, andcontrolled or used by, the party utilizing the cloud computingenvironment.

As used herein, the term “virtual asset” includes any virtualized entityor resource, and/or part of an actual, or “bare metal” entity requiringaccess to various resources, and types of resources. In variousembodiments, the virtual assets can be, but are not limited to, virtualmachines, virtual servers, and instances implemented in a cloudcomputing environment; databases implemented, or associated with, acloud computing environment, and/or instances implemented in a cloudcomputing environment; services associated with, and/or deliveredthrough, a cloud computing environment; communications systems usedwith, part of, or provided through, a cloud computing environment;and/or any other virtualized assets and/or sub-systems of “bare metal”physical devices such as mobile devices, remote sensors, laptops,desktops, point-of-sale devices, ATMs, electronic voting machines, etc.requiring access to various resources, and/or types of resources,located within a data center, within a cloud computing environment,and/or any other physical or logical location, as discussed herein,and/or as known/available in the art at the time of filing, and/or asdeveloped/made available after the time of filing.

As discussed below, in one embodiment, virtual asset creation data isgenerated through a virtual asset creation system such as a virtualasset template through which the creator of a virtual asset can generateoperational logic and assign resources and attributes to the virtualassets to be instantiated in a cloud computing environment, such as avirtual private cloud computing environment.

In one embodiment, a network communications device is included with eachcloud computing environment provided. In one embodiment, outgoingmessage traffic sent from one or more of the virtual assets associatedwith a given cloud computing environment to a destination external tothe cloud computing environment, such as the Internet, and/or incomingmessage traffic sent to one or more of the virtual assets associatedwith a given cloud computing environment from an origin external to thecloud computing environment, such as the Internet, is relayed throughthe network communications device for that cloud computing environment.

In various embodiments, the network communications devices for the cloudcomputing environment include, but are not limited to, one or more of aswitching system, such as a network switch; a router; a border router;any gateway system; a firewall system; a load balancing system; ahypervisor; or any communication, relay, or routing system, as discussedherein, and/or as known in the art at the time of filing, and/or asdeveloped after the time of filing, through which message traffic on anetwork communications channel to, or from, an external network, such asthe Internet, is relayed, and/or routed, to one or more virtual assetsin a cloud computing environment.

In one embodiment, the outgoing message traffic, and/or incoming messagetraffic, is relayed through the network communications device via atleast one communications channel, e.g., a network communicationschannel, herein also referred to as a first communications channel.

As noted above, in various embodiments, the outgoing, and/or incoming,message traffic to, and/or from, the virtual assets associated with agiven cloud computing environment are susceptible to the introduction ofmalware and, in particular, extrusion, and/or intrusion, relatedmalware.

As also noted above, the fact that malware can be introduced into thecloud computing environment is a long standing problem. As also notedabove, the introduction of malware into a virtual asset via one or moremessages included in message traffic relayed by the networkcommunications device, is known as intrusion. However, as also notedabove, once introduced, some forms of malware take control of some, orall, of the infected virtual asset functionality and use the virtualasset to send outgoing messages and data through the message trafficrelayed by the network communications device. This outbound malwaremechanism is referred to as extrusion.

Consequently, the detection of both malware intrusion and extrusion isan important part of making cloud computing environments more secure.However, as also noted above, a given cloud computing environment,and/or VPC, can include hundreds, thousands, or even millions, ofvirtual assets, owned or used by hundreds, thousands, or even millions,of parties. Consequently, detecting malware intrusion and extrusion in acloud computing environment is currently an extremely difficult andresource intensive task.

To address this issue, as discussed below, in one embodiment, one ormore virtual assets within, and/or assigned to, a cloud computingenvironment are provided a trigger monitoring system.

In one embodiment, by virtue of the addition of the trigger monitoringsystem logic to one or more of the one or more virtual assets in thecloud computing environment, the one or more virtual assets in the cloudcomputing environment provided a trigger monitoring system aretransformed into extrusion, and/or intrusion, detection capable virtualassets for the cloud computing environment.

In various embodiments, the trigger monitoring system is a module ofsoftware and/or logic implemented in, or on, the one or more virtualassets and capable of monitoring at least a portion of the messagetraffic to, and/or between, and/or from, one or more virtual assetsinstantiated in the cloud computing environment.

In various embodiments, the methods and systems for intrusion andextrusion detection discussed herein are applied to networkcommunications, e.g., message traffic, which is in plain text or isencrypted. Consequently, in some embodiments, the trigger monitoringsystem, and/or the network communications device, and/or the extrusion,and/or intrusion, detection capable virtual assets include a decryptioncapability to decrypt outgoing and incoming message traffic as part ofthe monitoring and analysis. In other embodiments, a decryptioncapability is provided to decrypt outgoing and incoming message trafficprior to being provided to trigger monitoring system and any monitoringand analysis.

As discussed below, in some embodiments, the trigger monitoring systemallows for analysis policies to be added, or removed, dynamically basedon alerts that are received.

Referring to FIG. 1, cloud computing environment 11 is shown, along withillustrative computing environments 10, 12, 13, 14, and 15. Herein,cloud computing environment 11 and computing environments 10, 12, 13,14, and 15 are referred to collectively as computing environments 10,11, 12, 13, 14, and 15.

Also shown in FIG. 1 is Internet 101 that, in this specific illustrativeexample, is the origin, and/or destination, external to cloud computingenvironment 11. As seen in FIG. 1, Internet 101 is communicativelycoupled to cloud computing environment 11 via network communicationschannel 114 and network communications device 115, shown in thisillustrative example as implemented computing environment 10.

As seen in FIG. 1, Internet 101 is communicatively coupled to networkcommunications device 115, through which message traffic to, and from,representative extrusion detection capable virtual asset 125 andrepresentative intrusion detection capable virtual asset 135 in cloudcomputing environment 11 is relayed via network communications channel114, also referred to herein as the first communications channel.

As seen in FIG. 1, network communications device 115 is shown asimplemented in computing environment 10 that is distinct from computingenvironment 11 of representative extrusion detection capable virtualasset 125 and representative intrusion detection capable virtual asset135. However, as noted above, this illustrative placement of networkcommunications device 115 is not limiting and, in other embodiments,network communications device 115 can be implemented in any of computingenvironments 10, 11, 12, 13, 14, and 15.

As also seen in FIG. 1, representative extrusion detection capablevirtual asset 125 and representative intrusion detection capable virtualasset 135 are provided with trigger monitoring system 127 and triggermonitoring system 137, respectively. Those of skill in the art willreadily recognize that while a single representative example of anextrusion detection capable virtual asset, i.e., extrusion detectioncapable virtual asset 125, is shown in FIG. 1, extrusion detectioncapable virtual asset 125 is representative of any number of extrusiondetection capable virtual assets that can be created and instantiated incloud computing environment 11. Likewise, while a single representativeexample of an intrusion detection capable virtual asset, i.e., intrusiondetection capable virtual asset 135, is shown in FIG. 1, intrusiondetection capable virtual asset 135 is representative of any number ofintrusion detection capable virtual assets that can be created andinstantiated in cloud computing environment 11.

In addition, in various embodiments, only extrusion detection capablevirtual assets are created and instantiated in cloud computingenvironment 11, and/or only intrusion detection capable virtual assetsare instantiated in cloud computing environment 11, and/or a mix ofextrusion detection capable virtual assets and intrusion detectioncapable virtual assets are created and instantiated in cloud computingenvironment 11.

In addition, in various embodiments, extrusion detection capable virtualasset 125 can include intrusion detection capabilities and intrusiondetection capable virtual asset 135 can include extrusion detectioncapabilities. Consequently, in various embodiments, extrusion detectioncapable virtual asset 125 and intrusion detection capable virtual asset135 are similar, or identical, extrusion/intrusion detection capablevirtual assets.

As discussed above, in one embodiment, virtual asset creation data isgenerated through a virtual asset creation system such as a virtualasset template through which the creator of a virtual asset can generateoperational logic and assign resources and attributes to the virtualassets to be instantiated in a cloud computing environment.

In addition to extrusion and intrusion capabilities for which virtualassets depicted and described herein may be configured, in variousembodiments, further disclosure is made regarding virtual assets havingself-monitoring and self-reporting characteristics and function. As oneof ordinary skill will readily appreciate, virtual assets may beconfigured to perform any or all of the features and process operationsdescribed herein.

FIG. 2 is a functional diagram of the interaction of various elementsassociated with exemplary embodiments of the methods and systems forproviding self-monitoring, self-reporting, and self-repairing virtualassets discussed herein.

Of particular note, the various elements/assets in FIG. 2 are shown forillustrative purposes as being associated with production environment200 and specific computing environments within production environment200, such as computing environments 210, 212, 213, 214, and 215.However, the exemplary placement of the various elements/assets withinthese environments and systems in FIG. 2 is made for illustrativepurposes only and, in various embodiments, any individual element/assetshown in FIG. 2, or combination of elements/assets shown in FIG. 2, canbe implemented and/or deployed on any of one or more various computingenvironments or systems, and/or architectural or infrastructurecomponents, such as one or more hardware systems, one or more softwaresystems, one or more data centers, more or more clouds or cloud types,one or more third party service capabilities, or any other computingenvironments, architectural, and/or infrastructure components, asdiscussed herein, and/or as known in the art at the time of filing,and/or as developed/made available after the time of filing.

In addition, the elements shown in FIG. 2, and/or the computingenvironments, systems and architectural and/or infrastructurecomponents, deploying the elements shown in FIG. 2, can be under thecontrol of, or otherwise associated with, various parties or entities,or multiple parties or entities, such as, but not limited to, the ownerof a data center, a party and/or entity providing all or a portion of acloud-based computing environment, the owner or a provider of anapplication or service, the owner or provider of one or more resources,and/or any other party and/or entity providing one or more functions,and/or any other party and/or entity as discussed herein, and/or asknown in the art at the time of filing, and/or as made known after thetime of filing.

In one embodiment, a production environment is provided for implementingan application. In particular, FIG. 2 shows a given application, e.g.,application 216 implemented in production environment 200 on server 253and using various assets.

As seen in FIG. 2, in this specific illustrative example, application216 is to be implemented using, and including, assets such as, but notlimited to, computing environments 210, 212, 213, 214, and 215, used toimplement application 216 in production environment 200, such as a datacenter, a cloud computing environment, and/or one or more othercomputing environments in which one or more assets and/or services usedto implement application 216 in production environment 200 are deployed.

As seen in FIG. 2, production environment 200 includes computingenvironment 210, for instance a local area network, or the Internet,that includes users 206 and 208 generating user data traffic 207 and209, respectively, using one or more computing systems (not shown). Asseen in FIG. 2, user data traffic 207 and 209 is provided to computingenvironment 212, such as an access layer or Internet Service Provider(ISP) service used to access application 216, via communications channel221.

As seen in FIG. 2, production environment 200 includes computingenvironment 212 which, in turn, includes, as illustrative examples, oneor more assets such as router 225, gateway 226, access control 227, andfirewall 228. As seen in FIG. 2, in this specific illustrative example,computing environment 212 is commutatively coupled to computingenvironment 213 of production environment 200 by communications channel230.

In the specific illustrative example of FIG. 2, computing environment213 of production environment 200 is a cloud computing environment andincludes representative self-monitoring, self-reporting, andself-repairing virtual assets 231 and 235 used to implement application216. Self-monitoring, self-reporting, and self-repairing virtual assets231 and 235 are discussed in more detail below.

In the specific illustrative example of FIG. 2, production environment200 includes computing environment 214, such as an access control layer,commutatively coupled to computing environment 213 by communicationschannel 241. In this specific illustrative example, computingenvironment 214 includes assets such as exemplary access controlsystems, e.g., one or more of access control 243, endpoint proxy 244,load balancer 245, and protocol endpoint 246.

As seen in the specific illustrative example of FIG. 2, productionenvironment 200 includes computing environment 215, such as a datacenter or infrastructure provider environment, commutatively coupled tocomputing environment 214 by communications channel 250. In thisspecific illustrative example, computing environment 215 includes assetssuch server 253 associated with application 216 and virtual assetmonitoring system 217. Virtual asset monitoring system 217 is discussedin more detail below.

In one embodiment, a cloud computing environment is provided. In variousembodiments, the provided cloud computing environment can be any form ofcloud computing environment, such as, but not limited to, a publiccloud; a private cloud; a virtual private network (VPN); a subnet; aVirtual Private Cloud (VPC); a sub-net or any security/communicationsgrouping; or any other cloud-based infrastructure, sub-structure, orarchitecture, as discussed herein, and/or as known in the art at thetime of filing, and/or as developed after the time of filing.

In one embodiment, one more self-monitoring and self-reporting virtualassets, and/or and self-monitoring, self-reporting, and self-repairingvirtual assets are provided in a production environment.

As noted above, as used herein, the term “virtual asset”, such as isused in the terms “self-monitoring and self-reporting virtual asset” and“self-monitoring, self-reporting, and self-repairing virtual asset”includes any virtualized entity or resource, and/or part of an actual,or “bare metal” entity.

As also noted above, in the specific illustrative example of FIG. 2,computing environment 213 is a cloud computing environment that is partof production environment 200 and includes representativeself-monitoring, self-reporting, and self-repairing virtual assets 231and 235 which also include, in one embodiment, any or all of thefeatures discussed herein as being part of extrusion detection capablevirtual asset 125 (FIG. 1) and representative intrusion detectioncapable virtual asset 135 (FIG. 1), for example.

As discussed in more detail below, in one embodiment, self-monitoring,self-reporting, and self-repairing virtual assets 231(FIG. 2) and 235include virtual asset self-monitoring logic 232 and 236, respectively.In one embodiment, virtual asset self-monitoring logic 232 and 236include data and instructions for detecting one or more trigger eventswithin self-monitoring, self-reporting, and self-repairing virtualassets 231 and 235, respectively.

As discussed in more detail below, in one embodiment, self-monitoring,self-reporting, and self-repairing virtual assets 231 and 235 includevirtual asset self-reporting logic 233 and 237, respectively. In oneembodiment, virtual asset self-reporting logic 233 and 237 includes dataand instructions for generating trigger event reporting data if one ofthe one or more trigger events is detected in self-monitoring,self-reporting, and self-repairing virtual assets 231 and 235 by virtualasset self-monitoring logic 232 and 236, respectively.

As discussed in more detail below, in one embodiment, self-monitoring,self-reporting, and self-repairing virtual assets 231 and 235 includevirtual asset self-reporting communications channel creation logic 234and 238, respectively. In one embodiment, virtual asset self-reportingcommunications channel creation logic 234 and 238 includes data andinstructions for opening a virtual asset self-reporting communicationschannel, such as virtual asset self-reporting communications channels252 and 251, respectively, between self-monitoring, self-reporting, andself-repairing virtual assets 231 and 235, respectively, and virtualasset monitoring system 217, if one of the one or more trigger events isdetected in self-monitoring, self-reporting, and self-repairing virtualassets 231 and 235 by the virtual asset self-monitoring logic 232 and236, respectively.

As seen in FIG. 2 and as discussed in more detail below, virtual assetmonitoring system 217 includes trigger event reporting data receiptmodule 219 for receiving trigger event reporting data fromself-monitoring, self-reporting, and self-repairing virtual assets 231and 235 if one of the one or more trigger events is detected inself-monitoring, self-reporting, and self-repairing virtual assets 231and 235 by the virtual asset self-monitoring logic 232 and 236,respectively.

As also seen in FIG. 2, and as discussed in more detail below, virtualasset monitoring system 217 includes responsive action implementationdata 218, which, in one embodiment, is provided to self-monitoring,self-reporting, and self-repairing virtual assets 231 and 235 inresponse to the receipt of trigger event data from self-monitoring,self-reporting, and self-repairing virtual assets 231 and 235.

In one embodiment, various types of trigger parameters representingtrigger events are predetermined and include message-related triggerparameters such as trigger parameters discussed herein as well as othertrigger parameters.

In various embodiments, the one or more trigger events defined caninclude, but are not limited to, one or more of: a network message froma virtual asset directed to a location known to be associated withmalicious entities, i.e., a black-listed destination; the frequency ofoutgoing network messages changing to a level above a defined thresholdlevel, i.e., the frequency of outgoing network messages changing to alevel deemed “not normal”; a response to a customer request beingdirected to a destination that is not the customer location of record; avirtual asset receiving a high-frequency of login attempts that fail; asize of the parameters sent into a virtual asset being outside a defined“normal” range of sizes for parameters; a size of outgoing networkmessages being outside a defined “normal” range of sizes of outgoingmessages; a total amount of data in any one communication connection ofa virtual asset exceeding a defined maximum normal size of acommunication to a customer; a request to a virtual asset coming in froma location known to be associated with malicious entities, i.e., ablack-listed origin location; an internal elapsed time of definedcritical operations changing to a time outside a defined range of“normal” values; and/or any other trigger event, or combination oftrigger events, as discussed herein, and/or as known in the art at thetime of filing, and/or as developed/made available after the time offiling.

In one embodiment, one or more trigger parameters are defined such thatif one or more of the one or more trigger parameters are detected in amessage to, or from, a virtual asset, then that message is deemed asuspect message that is potentially associated with an intrusion orextrusion attack on the virtual asset, and/or the cloud computingenvironment.

In various embodiments, the trigger parameters can be dynamically added,removed, and/or modified to reflect various policies, and/or policychanges made in response to malware alerts.

In various embodiments, specific examples of trigger parameters include,but are not limited to, the presence of an IP address in a messageindicating a designated suspect origin or destination. In oneembodiment, this trigger parameter is used to detect messages comingfrom, or going to, a designated suspicious entity that is suspected ofbeing associated with malware. In various embodiments, the IP addressesassociated with designated suspicious entities, and/or the identity ofthe entities themselves, is provided by one or more third parties viaalerts or other mechanisms.

In various embodiments, specific examples of trigger parameters include,but are not limited to, the presence of an IP address in a messageindicating a designated suspect geographical region. In one embodiment,this trigger parameter is used to detect messages coming from, or goingto, geographical locations that are known to be associated with malware.In various embodiments, the geographical locations known to beassociated with malware are provided by the one or more third partiesvia alerts or other mechanisms.

In various embodiments, specific examples of trigger parameters include,but are not limited to, the presence of an IP address in a messageindicating an origin or destination that is not included on a list ofauthorized, or expected, origins or destinations of messages to bereceived by, or transmitted from, the virtual assets. In one embodiment,this trigger parameter is used to detect message traffic that would notbe expected to be generated in the normal course of operation of thevirtual assets according to their operational mission.

In various embodiments, specific examples of trigger parameters include,but are not limited to, the presence of an IP address in a messageindicating a geographical location that is not included on a list ofauthorized, or expected, geographical locations to be associated withmessages to be received by, or transmitted from, and the virtual assets.In one embodiment, this trigger parameter is used to detect messagetraffic that would not be expected to be generated in the normal courseof operation of the virtual assets according to their operationalinstructions.

In various embodiments, specific examples of trigger parameters include,but are not limited to, setting a threshold maximum message size anddetermining that a given message is of a size exceeding the thresholdmaximum message size. In one embodiment, this trigger parameter takesadvantage of the fact that many forms of malware require message sizeslarger than those normally associated with a given virtual asset inorder to deliver the malware necessary to execute the malicious intent.

In various embodiments, specific examples of trigger parameters include,but are not limited to, setting a threshold minimum message size anddetermining that a given message is of a size that is less than thethreshold minimum message size. In one embodiment, this trigger is usedto detect messages of a size that is smaller than a message sizedetermined to be typical with respect to a given virtual asset, and thatare therefore suspicious.

In various embodiments, specific examples of trigger parameters include,but are not limited to, trigger parameters based on frequency analysisof the access pattern indicating that messages arrive too frequently ortoo infrequently.

In various embodiments, specific examples of trigger parameters include,but are not limited to, a hash value of at least part of the messagedata that is not included in a list of allowed hash values. In oneembodiment, this trigger parameter is used in conjunction with ahash-based analysis of at least part of a given message being sent to,and/or transmitted from, a virtual asset. In one embodiment, allowablehash values are defined and then a hash is performed on at least part ofa given message. In one embodiment, if the hash of the portion of thegiven message does not match any of the allowed hash values, the messageis determined to be suspect.

In various embodiments, specific examples of trigger parameters include,but are not limited to, an MD5 value of the message data that is notincluded in a list of allowed MD5 values.

MD5 (Message-Digest algorithm five) is a widely used cryptographic hashfunction producing a 128 bit (16 byte) hash value that is typicallyexpressed as a 32 digit hexadecimal number. In one embodiment, the MD5algorithm is applied to at least part of the message data associatedwith a given message and the resulting MD5 value is compared with a listof allowed MD5 values. If the resulting MD5 value does not match any ofthe allowed MD5 values, then the message is considered suspect.

In various embodiments, specific examples of trigger parameters include,but are not limited to, the specific identity of the sender of themessage and adding the ability to have a per-message offline analysisthat determines whether to trigger a message as suspect. In oneembodiment, the analysis can be in-line or asynchronously off-line andwould typically miss an initial or first example of an intrusion orextrusion message but would be used for other “like messages” where thecriteria for “like” is a trigger parameter that can be dynamicallyinstalled in the trigger monitoring system. Consequently, in oneembodiment, new trigger parameters are discovered and appliedheuristically to create a self-learning extrusion and/or intrusiondetection system.

In various embodiments, specific examples of trigger parameters include,but are not limited to, the specific identity of the recipient of themessage and adding the ability to have a per-message offline analysisthat determines whether to trigger a message as suspect. In oneembodiment, the analysis can be in-line or asynchronously off-line andwould typically miss an initial or first example of an intrusion orextrusion message but would be used for other “like messages” where thecriteria for “like” is a trigger parameter that can be dynamicallyinstalled in the trigger monitoring system. Consequently, in oneembodiment, new trigger parameters are discovered and appliedheuristically to create a self-learning extrusion and/or intrusiondetection system.

In various other embodiments, any other trigger parameter, orcombination of trigger parameters, as discussed herein, and/or as knownin the art at the time of filing, and/or as developed after the time offiling is/are defined.

In one embodiment, once the trigger parameters are defined,machine-readable trigger data is generated representing the triggerparameters.

In one embodiment, all, or part, of the trigger data is provided to thetrigger monitoring systems associated with the extrusion, and/orintrusion, detection capable virtual assets.

In one embodiment, the trigger data and the trigger monitoring systemsare then used to monitor at least part of the message data associatedwith at least some of the message traffic to, and/or from, the virtualassets relayed by the network communications device. In one embodiment,at least part of the message data associated with at least some of themessage traffic to, and/or from, the extrusion, and/or intrusion,detection capable virtual assets is monitored to detect one or more ofthe one or more trigger parameters within the message data.

In one embodiment, the part of the message data associated with at leastsome of the message traffic from the extrusion, and/or intrusion,detection capable virtual assets is decrypted by a decryption capabilityassociated with the trigger monitoring system, and/or the networkcommunications device, and/or the extrusion, and/or intrusion, detectioncapable virtual assets before the trigger data and the triggermonitoring systems are used to monitor at least part of the message dataassociated with at least some of the message traffic to and/or from theextrusion, and/or intrusion, detection capable virtual assets.

In one embodiment, if one or more of the one or more trigger parametersis detected within the message data associated with a given message, theclassification data associated with that message is transformed intoclassification data indicating that the detected message including oneor more of the one or more trigger parameters is a suspect message.

Returning to FIG. 1, trigger monitoring system 127 is shown implementedin extrusion detection capable virtual asset 125 and trigger monitoringsystem 137 is shown implemented in intrusion detection capable virtualasset 135.

As seen in FIG. 1, message copy data 129 is sent from extrusiondetection capable virtual asset 125 to threat scoring service 151,illustratively shown in computing environment 14 in FIG. 1, via threatscoring channel 150, also referred to as a second communicationschannel. Likewise, message copy data 139 is sent from intrusiondetection capable virtual asset 135 to threat scoring service 181,illustratively shown in computing environment 15 in FIG. 1, via threatscoring channel 180, also referred to as a second communicationschannel.

In one embodiment, threat scoring service 151 determines threat patternsfor potential security threats using any one of a number of techniques.In one embodiment, threat scoring service 151 requests and receivessecurity threat patterns from an information management security serviceprovider or vendor. Threat scoring service 151 then updates a securitythreat pattern database with the received security threat patterns. Inanother embodiment, computing security analysts manually update thesecurity threat pattern database through threat scoring service 151after compiling, reverse-engineering, or otherwise analyzing trafficpatterns between a malicious computing device and a service provider.For example, computing security analysts can simulate and monitortraffic patterns between a test computing system and a test assethosting a test online service by configuring the test computing systemto send or execute security threats on the test online service. Based onthe traffic patterns monitored from the simulation, the analysts candetermine and record particular patterns that are associated withparticular types of security threats. In some embodiments, the types ofthreats for which security threat patterns are stored in the securitythreat pattern database include, but are not limited to, spoofing,tampering, repudiation, information disclosure, denial of service,and/or elevation of privilege, among others.

Threat scoring service 151 can determine threat patterns or potentialsecurity threats by establishing baseline time limits for the reasonableexecution of one or more APIs associated with a virtual asset. Forexample, threat scoring service 151 can cause a virtual asset to executea sample program that cycles through one or more APIs of the virtualasset. During the execution of the sample program, Threat scoringservice 151 monitors the execution of the APIs and establishes minimumtime delays that are likely to occur or that should occur during normaland/or non-malicious communications with the virtual asset, according toone embodiment. Threat scoring service 151 can then record, create, ordetermine baseline or normal traffic patterns for the service trafficand can determine or define deviations from the baseline as securitythreat patterns, according to one embodiment. In some embodiments,threat scoring service 151 defines login failure patterns based on APIsassociated with login attempts, so that excessive attempts andexcessively short delays between successive attempts to login can beflagged as security threat patterns. In some embodiments, the patternsinclude, but are not limited to, time references, such as “FAST,”“SLOW,” “LONG,” “SHORT,” “QUICK,” “MEDIUM,” “VERY SLOW,” “VERY FAST,” orthe like. In other embodiments, the patterns include, but are notlimited to, bandwidth references and/or payload size references, suchas, “SMALL,” “MEDIUM,” “LARGE,” “VERY LARGE,” or the like.

Threat scoring service 151 can also determine defined anti-patterns, inone embodiment. By evaluating normal execution patterns of APIs for thevirtual asset for extended periods of time, threat scoring service 151can develop a sizable library in the threat scoring service 151 ofreasonable, allowable, and/or “normal” API execution sequences. Threatscoring service 151 can then define any traffic patterns that do not fitwithin the predetermined model as a subset of security threat patterns,i.e., anti-patterns. When an anti-pattern occurs, threat scoring service151 can flag or identify service traffic associated with theanti-pattern as being potentially malicious, according to oneembodiment.

In one embodiment, threat score data 153 is provided to extrusiondetection capable asset 125 via threat scoring channel 140, alsoreferred to as a second communications channel. Turning back to FIG. 1,in one embodiment, threat score data 183 is generated by threat scoringservice 181. In one embodiment, threat score data 183 is provided tointrusion detection capable virtual asset 135 via threat scoring channel190, also referred to as a second communications channel.

In FIG. 1, threat scoring service 151 is illustratively shown as beingimplemented in computing environment 14. As noted above, theimplementation of threat scoring service 151 in computing environment 14is shown for illustrative purposes only and, in other embodiments,threat scoring service 151 could be implemented in computing environment10, or computing environment 11, or computing environment 12, orcomputing environment 13, or computing environment 15, or partiallyimplemented in any one or more of computing environment 10, computingenvironment 11, computing environment 12, computing environment 13,computing environment 14, and computing environment 15.

In one embodiment, threat scoring services, such as representativethreat scoring services 151 and 181, are provided that are specificallyimplemented to analyze specific trigger parameters. Consequently, in oneembodiment, the particular threat scoring service to which a givenexample of suspect message data is transmitted is determined, at leastin part, by the specific trigger parameter detected in the suspectmessage from which the suspect message copy data was derived.Consequently, in one embodiment, the matching trigger data is used, atleast in part, to determine which analysis system, such asrepresentative threat scoring service 151, of one or more specializedanalysis systems (not shown) is to receive message copy data 129 viamessage analysis channel 160.

In various embodiments, threat scoring services, services, such asrepresentative threat scoring services 151 and 181, provide threat scoredata, such as representative threat score data 153 and 183 toextrusion/intrusion detection capable virtual assets such asrepresentative extrusion detection capable virtual asset 125 andintrusion detection capable virtual asset 135 at various frequencies. Inone embodiment, threat score data is transmitted to theextrusion/intrusion detection capable virtual assets on a periodic basisin digests, rather than in real time. In some embodiments, threat scoredata representing less significant potential threats are periodicallytransmitted to extrusion/intrusion detection capable virtual assets,e.g., on a weekly, semi-monthly, or monthly basis. In one embodiment,threat score data representing significant threats are immediatelytransmitted to the extrusion/intrusion detection capable virtual assets.

As seen in FIG. 1, message copy data 129 is sent from extrusiondetection capable virtual asset 125 to analysis system 161,illustratively shown in computing environment 12 in FIG. 1, via messageanalysis channel 160, also referred to as a third communicationschannel. Likewise, message copy data 139 is sent from intrusiondetection capable virtual asset 135 to analysis system 171,illustratively shown in computing environment 13 in FIG. 1, via messageanalysis channel 170, also referred to as a third communicationschannel.

Process

In accordance with one embodiment, a process for virtual asset assistedextrusion detection in a cloud computing environment includes providinga cloud computing environment. In one embodiment, the cloud computingenvironment includes one or more virtual assets. In one embodiment, oneor more of the one or more virtual assets in the cloud computingenvironment is provided a trigger monitoring system; therebytransforming the one or more virtual assets in the cloud computingenvironment provided a trigger monitoring system into extrusiondetection capable virtual assets for the cloud computing environment. Inone embodiment, one or more trigger parameters are defined and triggerdata representing the trigger parameters is generated. In oneembodiment, the trigger data is provided to the trigger monitoringsystems of the extrusion detection capable virtual assets. The triggermonitoring systems and the trigger data are then used to monitor atleast a portion of the message traffic sent from the virtual assets inthe cloud computing environment to detect any message including one ormore of the one or more trigger parameters.

In one embodiment, any detected message including one or more of the oneor more trigger parameters is identified as a suspect message and, foreach suspect message, suspect message copy data representing a copy ofat least a portion of the suspect message is generated. In oneembodiment, the suspect message copy data is then transferred to one ormore analysis systems for further analysis.

FIG. 3 is a flow chart of a process 300 for virtual asset assistedextrusion detection in a cloud computing environment in accordance withone embodiment. In one embodiment, process 300 for virtual assetassisted extrusion detection in a cloud computing environment begins atENTER OPERATION 301 of FIG. 3 and process flow proceeds to PROVIDE ACLOUD COMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUAL ASSETSOPERATION 303.

In one embodiment, at PROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDINGONE OR MORE VIRTUAL ASSETS OPERATION 303 a cloud computing environmentis provided.

In various embodiments, the cloud computing environment of PROVIDE ACLOUD COMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUAL ASSETSOPERATION 303 can be any form of cloud computing environment, such as,but not limited to, a Virtual Private Cloud, or VPC.

In many cases, a given application or service provided through a cloudcomputing environment may utilize, and interface with, multiple cloudcomputing environments, including multiple VPCs, in the course ofproviding the associated service. As noted above, each cloud computingenvironment includes allocated virtual assets associated with, andcontrolled or used by, the party utilizing the cloud computingenvironment.

As used herein, the term “virtual asset” includes any virtualized entityor resource, and/or part of an actual, or “bare metal” entity requiringaccess to various resources, and types of resources. In variousembodiments, the virtual assets can be, but are not limited to, virtualmachines, virtual servers, and instances implemented in a cloudcomputing environment; databases implemented, or associated with, acloud computing environment, and/or instances implemented in a cloudcomputing environment; services associated with, and/or deliveredthrough, a cloud computing environment; communications systems usedwith, part of, or provided through, a cloud computing environment;and/or any other virtualized assets and/or sub-systems of “bare metal”physical devices such as mobile devices, remote sensors, laptops,desktops, point-of-sale devices, ATMs, electronic voting machines, etc.requiring access to various resources, and/or types of resources,located within a data center, within a cloud computing environment,and/or any other physical or logical location, as discussed herein,and/or as known/available in the art at the time of filing, and/or asdeveloped/made available after the time of filing.

In one embodiment, virtual asset creation data is generated through avirtual asset creation system such as a virtual asset template throughwhich the creator of a virtual asset can generate operational logic andassign resources and attributes to the virtual assets to be instantiatedin a cloud computing environment, such as a virtual private cloudcomputing environment.

In one embodiment, once a cloud computing environment is provided atPROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUALASSETS OPERATION 303, process flow proceeds to PROVIDE ONE OR MORE OFTHE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE ORMORE VIRTUAL ASSETS INTO EXTRUSION DETECTION CAPABLE VIRTUAL ASSETSOPERATION 305.

In one embodiment, at PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS ATRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETSINTO EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 305 a networkcommunications device is provided for each cloud computing environmentof PROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUALASSETS OPERATION 303.

In various embodiments, the network communications devices of PROVIDEONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TOTRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO EXTRUSION DETECTIONCAPABLE VIRTUAL ASSETS OPERATION 305 provided for the cloud computingenvironment of PROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDING ONE ORMORE VIRTUAL ASSETS OPERATION 303 include, but are not limited to, oneor more of a switching system, such as a network switch; a router; aborder router; any gateway system; a firewall system; a load balancingsystem; a hypervisor; or any communication, relay, or routing system, asdiscussed herein, and/or as known in the art at the time of filing,and/or as developed after the time of filing, through which messagetraffic on a network communications channel to, or from, an externalnetwork, such as the Internet, is relayed, and/or routed, to one or morevirtual assets in a cloud computing environment.

In one embodiment, outgoing message traffic sent from one or more of thevirtual assets associated with a given cloud computing environment ofPROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUALASSETS OPERATION 303 to a destination external to the cloud computingenvironment, such as the Internet, is relayed through the networkcommunications device for that cloud computing environment of PROVIDEONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TOTRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO EXTRUSION DETECTIONCAPABLE VIRTUAL ASSETS OPERATION 305.

In one embodiment, the outgoing message traffic is relayed through thenetwork communications device of PROVIDE ONE OR MORE OF THE VIRTUALASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUALASSETS INTO EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 305 viaat least one communications channel, e.g., a network communicationschannel, herein also referred to as a first communications channel.

As noted above, in various embodiments, the outgoing message trafficfrom the virtual assets associated with a given cloud computingenvironment of PROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDING ONE ORMORE VIRTUAL ASSETS OPERATION 303 are susceptible to the introduction ofmalware and, in particular, extrusion related malware.

As also noted above, the fact that malware can be introduced into thecloud computing environments of PROVIDE A CLOUD COMPUTING ENVIRONMENTINCLUDING ONE OR MORE VIRTUAL ASSETS OPERATION 303 is a long standingproblem. As also noted above, some forms of malware take control ofsome, or all, of the infected virtual asset functionality and use thevirtual asset to send outgoing messages and data through the messagetraffic relayed by the network communications device. This outboundmalware mechanism is referred to as extrusion.

Consequently, the detection of malware extrusion is an important part ofmaking the cloud computing environments of PROVIDE A CLOUD COMPUTINGENVIRONMENT INCLUDING ONE OR MORE VIRTUAL ASSETS OPERATION 303 moresecure. However, as also noted above, a given cloud computingenvironment, and/or virtual private cloud computing environment, caninclude hundreds, thousands, or even millions, of virtual assets, ownedor used by hundreds, thousands, or even millions, of parties.Consequently, detecting malware extrusion in a cloud computingenvironment is currently an extremely difficult and resource intensivetask.

To address this issue, in one embodiment, at PROVIDE ONE OR MORE OF THEVIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MOREVIRTUAL ASSETS INTO EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION305 one or more virtual assets within, and/or assigned to, the cloudcomputing environment of PROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDINGONE OR MORE VIRTUAL ASSETS OPERATION 303 are provided a triggermonitoring system.

In one embodiment, by virtue of the addition of the trigger monitoringsystem logic to one or more of the one or more virtual assets in thecloud computing environment at PROVIDE ONE OR MORE OF THE VIRTUAL ASSETSA TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETSINTO EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 305, the oneor more virtual assets in the cloud computing environment provided atrigger monitoring system are transformed into extrusion detectioncapable virtual assets for the cloud computing environment.

In various embodiments, the trigger monitoring system of PROVIDE ONE ORMORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THEONE OR MORE VIRTUAL ASSETS INTO EXTRUSION DETECTION CAPABLE VIRTUALASSETS OPERATION 305 is a module of software and/or logic implementedin, or on, the one or more virtual assets and capable of monitoring atleast a portion of the message traffic from one or more virtual assetsinstantiated in the cloud computing environment.

In various embodiments, process 300 for virtual asset assisted extrusiondetection in a cloud computing environment is applied to networkcommunications, e.g., message traffic, which is in plain text or isencrypted. Consequently, in some embodiments, the trigger monitoringsystem, and/or the network communications device, and/or the extrusiondetection capable virtual assets of PROVIDE ONE OR MORE OF THE VIRTUALASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUALASSETS INTO EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 305include a decryption capability to decrypt outgoing message traffic aspart of the monitoring and analysis. In other embodiments, a decryptioncapability is provided to decrypt outgoing message traffic prior tobeing provided to trigger monitoring system and any monitoring andanalysis.

As discussed below, in some embodiments, the trigger monitoring systemof PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEMTO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO EXTRUSION DETECTIONCAPABLE VIRTUAL ASSETS OPERATION 305 allows for analysis policies to beadded, or removed, dynamically based on alerts that are received.

In one embodiment, once one or more virtual assets within, and/orassigned to, the cloud computing environment of PROVIDE A CLOUDCOMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUAL ASSETS OPERATION 303are provided a trigger monitoring system at PROVIDE ONE OR MORE OF THEVIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MOREVIRTUAL ASSETS INTO EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION305, process flow proceeds to DEFINE ONE OR MORE TRIGGER PARAMETERSOPERATION 307.

In one embodiment, at DEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION307 one or more trigger parameters are defined such that if one or moreof the one or more trigger parameters are detected in a message from avirtual asset, then that message is deemed a suspect message that ispotentially associated with an extrusion attack on the virtual asset,and/or the cloud computing environment.

In various embodiments, the trigger parameters of DEFINE ONE OR MORETRIGGER PARAMETERS OPERATION 307 can be dynamically added, removed,and/or modified to reflect various policies, and/or policy changes, madein response to malware alerts. In addition, as discussed below, in oneembodiment, trigger parameters are applied heuristically and new triggerparameters that are discovered by the application of process 300 forvirtual asset assisted extrusion detection in a cloud computingenvironment are added to create a self-learning extrusion detectionsystem.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 307 include, but are notlimited to, the presence of an IP address in a message indicating adesignated suspect destination. In one embodiment, this triggerparameter is used to detect messages going to a designated suspiciousentity that is suspected of being associated with malware. In variousembodiments, the IP addresses associated with designated suspiciousentities, and/or the identity of the entities themselves, is provided byone or more third parties via alerts or other mechanisms.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 307 include, but are notlimited to, the presence of an IP address in a message indicating adesignated suspect geographical region. In one embodiment, this triggerparameter is used to detect messages going to geographical locationsthat are known to be associated with malware. In various embodiments,the geographical locations known to be associated with malware areprovided by the one or more third parties via alerts or othermechanisms.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 307 include, but are notlimited to, the presence of an IP address in a message indicating adestination that is not included on a list of authorized, or expected,destinations of messages transmitted from the virtual assets. In oneembodiment, this trigger parameter is used to detect message trafficthat would not be expected to be generated in the normal course ofoperation of the virtual assets according to their operational mission.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 307 include, but are notlimited to, the presence of an IP address in a message indicating ageographical location that is not included on a list of authorized, orexpected, geographical locations to be associated with messages to betransmitted from the virtual assets. In one embodiment, this triggerparameter is used to detect message traffic that would not be expectedto be generated in the normal course of operation of the virtual assetsaccording to their operational instructions.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 307 include, but are notlimited to, setting a threshold maximum message size and determiningthat the size of a given message exceeds the threshold maximum messagesize. In one embodiment, this trigger parameter takes advantage of thefact that many forms of malware require message sizes larger than thosenormally associated with a given virtual asset in order to deliver themalware necessary to execute the malicious intent associated with themalware.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 307 include, but are notlimited to, setting a threshold minimum message size and determiningthat the size of a given message is less than the threshold minimummessage size. In one embodiment, this trigger is used to detect messagesthat are smaller than a message size determined to be typical withrespect to a given virtual asset, and that are therefore suspicious.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 307 include, but are notlimited to, trigger parameters based on frequency analysis of the accesspattern indicating that messages arrive too frequently or tooinfrequently.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 307 include, but are notlimited to, a hash value of at least part of the message data that isnot included in a list of allowed hash values. In one embodiment, thistrigger parameter is used in conjunction with a hash-based analysis ofat least part of a given message being transmitted from a virtual asset.In one embodiment, allowable hash values are defined and then a hash isperformed on at least part of a given message. In one embodiment, if thehash of the portion of the given message does not match any of theallowed hash values, the message is determined to be suspect.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 307 include, but are notlimited to, an MD5 value of the message data that is not included in alist of allowed MD5 values.

MD5 (Message-Digest algorithm five) is a widely used cryptographic hashfunction producing a 128 bit (16 byte) hash value that is typicallyexpressed as a 32 digit hexadecimal number. In one embodiment, the MD5algorithm is applied to at least part of the message data associatedwith a given message and the resulting MD5 value is compared with a listof allowed MD5 values. If the resulting MD5 value does not match any ofthe allowed MD5 values, then the message is considered suspect.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 307 include, but are notlimited to, the specific identity of the sender of the message andadding the ability to have a per-message offline analysis thatdetermines whether to trigger a message as suspect. In one embodiment,the analysis can be in-line or asynchronously off-line and wouldtypically miss an initial or first example of an extrusion message butwould be used for other “like messages” where the criteria for “like” isa trigger parameter that can be dynamically installed in the triggermonitoring system. In addition, as discussed below, in one embodiment,trigger parameters are applied heuristically and new trigger parametersthat are discovered by the application of process 300 for virtual assetassisted extrusion detection in a cloud computing environment are addedto create a self-learning extrusion detection system.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 307 include, but are notlimited to, the specific identity of the recipient of the message andadding the ability to have a per-message offline analysis thatdetermines whether to trigger a message as suspect. In one embodiment,the analysis can be in-line or asynchronously off-line and wouldtypically miss an initial or first example of an extrusion message butwould be used for other “like messages” where the criteria for “like” isa trigger parameter that can be dynamically installed in the triggermonitoring system. In addition, as discussed below, in one embodiment,trigger parameters are applied heuristically and new trigger parametersthat are discovered by the application of process 300 for virtual assetassisted extrusion detection in a cloud computing environment are addedto create a self-learning extrusion detection system.

In various other embodiments, any other trigger parameter, orcombination of trigger parameters, as discussed herein, and/or as knownin the art at the time of filing, and/or as developed after the time offiling is/are defined at DEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION307.

As noted above, in one embodiment, trigger parameters are appliedheuristically and new trigger parameters that are discovered by theapplication of process 300 for virtual asset assisted extrusiondetection in a cloud computing environment are added to create aself-learning extrusion detection system.

In one embodiment, once one or more trigger parameters are defined atDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 307, process flowproceeds to GENERATE TRIGGER DATA REPRESENTING THE TRIGGER PARAMETERSOPERATION 309.

In one embodiment, at GENERATE TRIGGER DATA REPRESENTING THE TRIGGERPARAMETERS OPERATION 309 machine-readable trigger data is generatedrepresenting the trigger parameters of DEFINE ONE OR MORE TRIGGERPARAMETERS OPERATION 307.

In one embodiment, once machine-readable trigger data is generatedrepresenting the trigger parameters of DEFINE ONE OR MORE TRIGGERPARAMETERS OPERATION 307 at GENERATE TRIGGER DATA REPRESENTING THETRIGGER PARAMETERS OPERATION 309, process flow proceeds PROVIDE THETRIGGER DATA TO THE TRIGGER MONITORING SYSTEMS OF THE EXTRUSIONDETECTION CAPABLE VIRTUAL ASSETS OPERATION 311.

In one embodiment, at PROVIDE THE TRIGGER DATA TO THE TRIGGER MONITORINGSYSTEMS OF THE EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 311at least part of the trigger data of GENERATE TRIGGER DATA REPRESENTINGTHE TRIGGER PARAMETERS OPERATION 309 is provided to the triggermonitoring systems of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS ATRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETSINTO EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 305.

In one embodiment, once at least part of the trigger data of GENERATETRIGGER DATA REPRESENTING THE TRIGGER PARAMETERS OPERATION 309 isprovided to the trigger monitoring systems of PROVIDE ONE OR MORE OF THEVIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MOREVIRTUAL ASSETS INTO EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION305 at PROVIDE THE TRIGGER DATA TO THE TRIGGER MONITORING SYSTEMS OF THEEXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 311, process flowproceeds to USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGER DATA TOMONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT FROM EACH OF THEEXTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 313.

In one embodiment, at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGERDATA TO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT FROM EACHOF THE EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 313 thetrigger data of GENERATE TRIGGER DATA REPRESENTING THE TRIGGERPARAMETERS OPERATION 309 and the trigger monitoring system of PROVIDEONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TOTRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO EXTRUSION DETECTIONCAPABLE VIRTUAL ASSETS OPERATION 305 are used to monitor at least partof the message data associated with at least some of the extrusiondetection capable virtual assets of PROVIDE ONE OR MORE OF THE VIRTUALASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUALASSETS INTO EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 305.

In one embodiment, at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGERDATA TO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT FROM EACHOF THE EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 313 the atleast part of the message data associated with at least some of themessage traffic from the extrusion detection capable virtual assets isdecrypted by the decryption capability associated with the triggermonitoring system of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGERMONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTOEXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 305 before thetrigger data of GENERATE TRIGGER DATA REPRESENTING THE TRIGGERPARAMETERS OPERATION 309 and the trigger monitoring system of PROVIDEONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TOTRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO EXTRUSION DETECTIONCAPABLE VIRTUAL ASSETS OPERATION 305 are used to monitor at least partof the message data associated with at least some of the message trafficfrom the extrusion detection capable virtual assets of PROVIDE ONE ORMORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THEONE OR MORE VIRTUAL ASSETS INTO EXTRUSION DETECTION CAPABLE VIRTUALASSETS OPERATION 305.

In one embodiment, at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGERDATA TO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT FROM EACHOF THE EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 313 a samplepart of the message data associated with at least some of the messagetraffic from at least some of the extrusion detection capable virtualassets of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORINGSYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO EXTRUSIONDETECTION CAPABLE VIRTUAL ASSETS OPERATION 305 is monitored to detectone or more of the one or more trigger parameters within the messagedata.

In one embodiment, at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGERDATA TO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT FROM EACHOF THE EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 313 all of themessage data from at least some of the extrusion detection capablevirtual assets of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGERMONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTOEXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 305 is monitored todetect one or more of the one or more trigger parameters within themessage data.

In one embodiment, at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGERDATA TO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT FROM EACHOF THE EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 313 at leastpart of the message data from all of the extrusion detection capablevirtual assets of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGERMONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTOEXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 305 is monitored todetect one or more of the one or more trigger parameters within themessage data.

In one embodiment, at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGERDATA TO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT FROM EACHOF THE EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 313 all of themessage data associated with all of the extrusion detection capablevirtual assets of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGERMONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTOEXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 305 is monitored todetect one or more of the one or more trigger parameters within themessage data.

In one embodiment, the analysis of USE THE TRIGGER MONITORING SYSTEMSAND THE TRIGGER DATA TO MONITOR AT LEAST A PORTION OF THE MESSAGETRAFFIC SENT FROM EACH OF THE EXTRUSION DETECTION CAPABLE VIRTUAL ASSETSTO DETECT ANY MESSAGE INCLUDING ONE OR MORE OF THE TRIGGER PARAMETERSOPERATION 313 is performed by the trigger monitoring systems in-line, orasynchronously off-line, on a per-message basis. Consequently, in someembodiments, an initial or first example of an extrusion message ispassed through a given extrusion detection capable virtual asset butwould be used to stop other “like messages” where the criteria for“like” is a trigger parameter that can be dynamically installed in thetrigger monitoring system.

In addition, in one embodiment, trigger parameters are appliedheuristically at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGER DATATO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT FROM EACH OFTHE EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 313 and newtrigger parameters that are discovered by the application of process 300for virtual asset assisted extrusion detection in a cloud computingenvironment are added to create a self-learning extrusion detectionsystem.

In one embodiment, once the trigger data of GENERATE TRIGGER DATAREPRESENTING THE TRIGGER PARAMETERS OPERATION 309 and the triggermonitoring system of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGERMONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTOEXTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 305 are used tomonitor at least part of the message data associated with at least someof the extrusion detection capable virtual assets of PROVIDE ONE OR MOREOF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONEOR MORE VIRTUAL ASSETS INTO EXTRUSION DETECTION CAPABLE VIRTUAL ASSETSOPERATION 305 at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGER DATATO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT FROM EACH OFTHE EXTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 313, processflow proceeds to CLASSIFY ANY DETECTED MESSAGE INCLUDING ONE OR MORE OFTHE TRIGGER PARAMETERS AS A SUSPECT MESSAGE OPERATION 315.

In one embodiment, at CLASSIFY ANY DETECTED MESSAGE INCLUDING ONE ORMORE OF THE TRIGGER PARAMETERS AS A SUSPECT MESSAGE OPERATION 315, ifone or more of the one or more trigger parameters of DEFINE ONE OR MORETRIGGER PARAMETERS OPERATION 307 is detected within the message dataassociated with a given message, the classification data associated withthat message is transformed into classification data indicating that thedetected message including one or more of the one or more triggerparameters is a suspect message.

In one embodiment, once the classification data associated with messageshaving one or more of the one or more trigger parameters of DEFINE ONEOR MORE TRIGGER PARAMETERS OPERATION 307 is transformed intoclassification data indicating that the detected message including oneor more of the one or more trigger parameters is a suspect message atCLASSIFY ANY DETECTED MESSAGE INCLUDING ONE OR MORE OF THE TRIGGERPARAMETERS AS A SUSPECT MESSAGE OPERATION 315, process flow proceeds toASSIGN A THREAT SCORE TO THE SUSPECT MESSAGE AT LEAST PARTIALLY BASED ONA POTENTIAL IMPACT OF THE SUSPECT MESSAGE'S POTENTIAL SECURITY THREAT ONTHE EXTRUSION DETECTION CAPABLE VIRTUAL ASSET OPERATION 317. In oneembodiment, at ASSIGN A THREAT SCORE TO THE SUSPECT MESSAGE AT LEASTPARTIALLY BASED ON A POTENTIAL IMPACT OF THE SUSPECT MESSAGE'S POTENTIALSECURITY THREAT ON THE EXTRUSION DETECTION CAPABLE VIRTUAL ASSETOPERATION 317, a threat score is assigned to the suspect message based,at least partially, on a potential impact of the suspect message'spotential security threat on the extrusion detection capable virtualasset.

For example, if the potential security threat can compromise financialdata, e.g., credit card information of users, the threat score will behigher than if the potential security threats cause minor decreases innetwork connectivity speeds, according to one embodiment. To determinethe potential impact of the potential security threat, the processevaluates the context of the potential security threat. In other words,the process evaluates the characteristics of the extrusion detectioncapable virtual asset, the type of threat, the likelihood of success ofthe threat, and the like.

In one embodiment, a threat score is assigned to the suspect messagebased on the relative impact of a potential security threat to theextrusion detection capable virtual asset. For example, based on theimpact of the potential security threat, a numerical score can beassigned to the suspect message. For example, a score of 10 can beassigned to suspect messages having potential security threats with thehighest probability of successful attack and that acquire personal dataof users of the extrusion detection capable virtual asset. A 0 (zero)can be assigned to suspect messages having potential security threatswith the lowest probability of successful attack and/or that are likelyto have a negligible effect on the performance of the extrusiondetection capable virtual asset, according to one embodiment. Variousfactors, such as asset configuration, number of subscribers, securityfeatures developed into the extrusion detection capable virtual asset,notification of new security threats or external risks, or input from athird party vulnerability scanner, can provide context while assessing apotential security threat and assigning a threat score. In someembodiments, the threat scores range from 0 to 10. In other embodiments,the threat scores range from 0 to 100. In yet other embodiments, thethreat scores include values or indicators such as, “LOW,” “MEDIUM,” and“HIGH.” In one embodiment, the threat scores can include colorcoordinating so that high priority potential security threats are afirst color such as red, low priority potential security threats are asecond color different from the first color, such as orange, and theabsence of potential security threats is indicated with a third colordifferent from the first and second colors, such as green. As those ofskill in the art will appreciate, other scoring ranges or values can beused while assigning a threat score to a suspect message having apotential security threat, according to various embodiments.

In one embodiment, once a threat score is assigned to the suspectmessage at ASSIGN A THREAT SCORE TO THE SUSPECT MESSAGE AT LEASTPARTIALLY BASED ON A POTENTIAL IMPACT OF THE SUSPECT MESSAGE'S POTENTIALSECURITY THREAT ON THE EXTRUSION DETECTION CAPABLE VIRTUAL ASSETOPERATION 317, process flow proceeds to PROVIDE THE THREAT SCORE TO THEEXTRUSION DETECTION CAPABLE VIRTUAL ASSET TO ENABLE THE EXTRUSIONDETECTION CAPABLE VIRTUAL ASSET TO SECURE AGAINST THE POTENTIAL SECURITYTHREAT OPERATION 319.

In one embodiment, at PROVIDE THE THREAT SCORE TO THE EXTRUSIONDETECTION CAPABLE VIRTUAL ASSET TO ENABLE THE EXTRUSION DETECTIONCAPABLE VIRTUAL ASSET TO SECURE AGAINST THE POTENTIAL SECURITY THREATOPERATION 319, the threat score is provided to the extrusion detectioncapable virtual asset to enable the extrusion detection capable virtualasset to secure against the potential security threat.

In some embodiments, threat scores associated with suspect messages areprovided to the extrusion detection capable virtual assets on a periodicbasis in digests, rather than in real time. In some embodiments, threatscores between 0 and 5 are periodically provided to the extrusiondetection capable virtual assets, e.g., on a weekly, semi-monthly, ormonthly basis. In one embodiment, threat scores of between 8 and 10 areimmediately provided to the extrusion detection capable virtual assets.In one embodiment, threat scores are provided to the extrusion detectioncapable virtual assets according to the computing resources and humanresources available.

The threat scores are provided to the extrusion detection capablevirtual assets for consideration and/or remedial action, according toone embodiment. In some embodiments, one or more identifiers, e.g., anIP address, involved in the potential security threat are provided tothe extrusion detection capable virtual assets to allow the extrusiondetection capable virtual assets to block future communicationsassociated with the suspect message.

In one embodiment, the extrusion detection capable virtual asset securesagainst the potential security threat by submitting the security threatto disciplinary authorities to track down and punish the author(s) ofthe security threat. In other embodiments, the extrusion detectioncapable virtual asset secures against the potential security threat byblocking access of one or more computing systems to the extrusiondetection capable virtual asset.

In one embodiment, once the threat score is provided to the extrusiondetection capable virtual asset at PROVIDE THE THREAT SCORE TO THEEXTRUSION DETECTION CAPABLE VIRTUAL ASSET TO ENABLE THE EXTRUSIONDETECTION CAPABLE VIRTUAL ASSET TO SECURE AGAINST THE POTENTIAL SECURITYTHREAT OPERATION 319, process flow proceeds to FOR EACH SUSPECT MESSAGEGENERATE SUSPECT MESSAGE COPY DATA REPRESENTING A COPY OF AT LEAST APORTION OF THE SUSPECT MESSAGE OPERATION 321.

In one embodiment, the detected suspect messages of CLASSIFY ANYDETECTED MESSAGE INCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS AS ASUSPECT MESSAGE OPERATION 315 are temporarily permitted to betransmitted from the virtual assets through the network communicationschannel with minimal delay.

In one embodiment, this transmission is permitted in order to avoidsignificantly disrupting or delaying the transmission of messageswithout further evidence that the suspect messages are indeed malicious.However, in one embodiment, at FOR EACH SUSPECT MESSAGE GENERATE SUSPECTMESSAGE COPY DATA REPRESENTING A COPY OF AT LEAST A PORTION OF THESUSPECT MESSAGE OPERATION 321, for each detected suspect message ofCLASSIFY ANY DETECTED MESSAGE INCLUDING ONE OR MORE OF THE TRIGGERPARAMETERS AS A SUSPECT MESSAGE OPERATION 315, suspect message copy datais generated representing a copy of at least part of the message datamaking up the suspect message.

In one embodiment, for each detected suspect message of CLASSIFY ANYDETECTED MESSAGE INCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS AS ASUSPECT MESSAGE OPERATION 315, the at least part of the message datamaking up the suspect message is decrypted and decrypted suspect messagecopy data is generated representing a decrypted copy of at least part ofthe message data making up the suspect message at FOR EACH SUSPECTMESSAGE GENERATE SUSPECT MESSAGE COPY DATA REPRESENTING A COPY OF ATLEAST A PORTION OF THE SUSPECT MESSAGE OPERATION 321.

In one embodiment, once for each detected suspect message of CLASSIFYANY DETECTED MESSAGE INCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS ASA SUSPECT MESSAGE OPERATION 315, suspect message copy data is generatedrepresenting a copy of at least part of the message data making up thesuspect message at FOR EACH SUSPECT MESSAGE GENERATE SUSPECT MESSAGECOPY DATA REPRESENTING A COPY OF AT LEAST A PORTION OF THE SUSPECTMESSAGE OPERATION 321, process flow proceeds to TRANSFER THE SUSPECTMESSAGE COPY DATA TO ONE OR MORE ANALYSIS SYSTEMS FOR FURTHER ANALYSISOPERATION 323.

In one embodiment, at TRANSFER THE SUSPECT MESSAGE COPY DATA TO ONE ORMORE ANALYSIS SYSTEMS FOR FURTHER ANALYSIS OPERATION 323, the suspectmessage copy data of FOR EACH SUSPECT MESSAGE GENERATE SUSPECT MESSAGECOPY DATA REPRESENTING A COPY OF AT LEAST A PORTION OF THE SUSPECTMESSAGE OPERATION 321 is transmitted to one or more analysis systems forfurther analysis in an “off-line” environment.

In one embodiment, at TRANSFER THE SUSPECT MESSAGE COPY DATA TO ONE ORMORE ANALYSIS SYSTEMS FOR FURTHER ANALYSIS OPERATION 323, the suspectmessage copy data of FOR EACH SUSPECT MESSAGE GENERATE SUSPECT MESSAGECOPY DATA REPRESENTING A COPY OF AT LEAST A PORTION OF THE SUSPECTMESSAGE OPERATION 321 is transmitted to the one or more analysis systemsvia a message analysis channel, also referred to herein as a thirdcommunications channel, that is distinct from the network communicationschannel, i.e., the first communications channel through which messagesare transmitted from the virtual assets relayed by the networkcommunications device of PROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDINGONE OR MORE VIRTUAL ASSETS OPERATION 303. In this way, the transmissionof the suspect message copy data, and the subsequent message dataanalysis, does not affect the operation of the virtual asset, and/or thecloud computing environment, application, service, enterprise, and/orinfrastructure associated with the virtual asset.

In one embodiment, multiple analysis systems are provided at TRANSFERTHE SUSPECT MESSAGE COPY DATA TO ONE OR MORE ANALYSIS SYSTEMS FORFURTHER ANALYSIS OPERATION 323 that are specifically implemented toanalyze specific trigger parameters of DEFINE ONE OR MORE TRIGGERPARAMETERS OPERATION 307.

Consequently, in one embodiment, the particular analysis system to whicha given example of suspect message data is transmitted at TRANSFER THESUSPECT MESSAGE COPY DATA TO ONE OR MORE ANALYSIS SYSTEMS FOR FURTHERANALYSIS OPERATION 323 is determined, at least in part, by the specifictrigger parameter detected in the suspect message at USE THE TRIGGERMONITORING SYSTEMS AND THE TRIGGER DATA TO MONITOR AT LEAST A PORTION OFTHE MESSAGE TRAFFIC SENT FROM EACH OF THE EXTRUSION DETECTION CAPABLEVIRTUAL ASSETS TO DETECT ANY MESSAGE INCLUDING ONE OR MORE OF THETRIGGER PARAMETERS OPERATION 313 from which the suspect message copydata was derived at FOR EACH SUSPECT MESSAGE GENERATE SUSPECT MESSAGECOPY DATA REPRESENTING A COPY OF AT LEAST A PORTION OF THE SUSPECTMESSAGE OPERATION 321.

In one embodiment, if, as a result of the analysis of the suspectmessage copy data by one or more of the analysis systems at TRANSFER THESUSPECT MESSAGE COPY DATA TO ONE OR MORE ANALYSIS SYSTEMS FOR FURTHERANALYSIS OPERATION 323, it is determined that the suspect message isindeed associated with an extrusion attack, one or more systems,entities, and/or parties, are alerted to the situation so thatappropriate protective action can be taken.

In one embodiment, if, as a result of the analysis of the suspectmessage copy data by one or more of the analysis systems at TRANSFER THESUSPECT MESSAGE COPY DATA TO ONE OR MORE ANALYSIS SYSTEMS FOR FURTHERANALYSIS OPERATION 323, it is determined that the suspect message isindeed associated with an extrusion attack, one or more protectiveactions are automatically taken to prevent further infection of thevirtual assets, and/or other virtual assets, and/or the cloud computingenvironment, application, service, infrastructure, or computingenvironment, associated with the now identified infected virtual asset.

In various embodiments, the protective actions taken can include, butare not limited to, isolating the virtual asset such that the virtualasset can still continue to operate, but in total isolation of all othervirtual assets; partially isolating the virtual asset such that thevirtual asset is allowed to connect to some very specific virtualassets, but has most of its communication channels blocked; “killing” orterminating the virtual asset; repairing the virtual asset by re-loadingthe compromised sub-components of the virtual asset; and/or any otherprotective actions, or combination of protective actions, discussedherein, and/or as known in the art at the time of filing, and/or asdeveloped, or become known, after the time of filing.

In addition, trigger parameters are applied heuristically at USE THETRIGGER MONITORING SYSTEMS AND THE TRIGGER DATA TO MONITOR AT LEAST APORTION OF THE MESSAGE TRAFFIC SENT FROM EACH OF THE EXTRUSION DETECTIONCAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGE INCLUDING ONE OR MORE OFTHE TRIGGER PARAMETERS OPERATION 313 and if, as a result of the analysisof the suspect message copy data by one or more of the analysis systemsat TRANSFER THE SUSPECT MESSAGE COPY DATA TO ONE OR MORE ANALYSISSYSTEMS FOR FURTHER ANALYSIS OPERATION 323, it is determined that thesuspect message is indeed associated with an extrusion attack, newtrigger parameters that are thereby discovered by the application ofprocess 300 for virtual asset assisted extrusion detection in a cloudcomputing environment are added to create a self-learning extrusiondetection system.

In one embodiment, once the suspect message copy data of FOR EACHSUSPECT MESSAGE GENERATE SUSPECT MESSAGE COPY DATA REPRESENTING A COPYOF AT LEAST A PORTION OF THE SUSPECT MESSAGE OPERATION 321 istransmitted to one or more analysis systems for further analysis in an“off-line” environment at TRANSFER THE SUSPECT MESSAGE COPY DATA TO ONEOR MORE ANALYSIS SYSTEMS FOR FURTHER ANALYSIS OPERATION 323, processflow proceeds to EXIT OPERATION 330.

In one embodiment, at EXIT OPERATION 330 process 300 for virtual assetassisted extrusion detection in a cloud computing environment is exitedto await new data.

Using process 300 for virtual asset assisted extrusion detection in acloud computing environment discussed above, extrusion attacks can bedetected using largely existing cloud computing environmentinfrastructure, such as modified virtual assets with added triggermonitoring systems; without the need for devoting extensive and/orspecialized resources. Consequently, using process 300 for virtual assetassisted extrusion detection in a cloud computing environment, extrusionevents can be efficiently and effectively detected; thereby makingdistributed computing environments, such as cloud computingenvironments, more secure.

In accordance with one embodiment, a process for virtual asset assistedintrusion detection in a cloud computing environment includes providinga cloud computing environment. In one embodiment, the cloud computingenvironment includes one or more virtual assets. In one embodiment, oneor more of the one or more virtual assets in the cloud computingenvironment is provided a trigger monitoring system; therebytransforming the one or more virtual assets in the cloud computingenvironment provided a trigger monitoring system into intrusiondetection capable virtual assets for the cloud computing environment. Inone embodiment, one or more trigger parameters are defined and triggerdata representing the trigger parameters is generated. In oneembodiment, the trigger data is provided to the trigger monitoringsystems of the intrusion detection capable virtual assets. The triggermonitoring systems and the trigger data are then used to monitor atleast a portion of the message traffic sent to the virtual assets in thecloud computing environment to detect any message including one or moreof the one or more trigger parameters.

In one embodiment, any detected message including one or more of the oneor more trigger parameters is identified as a suspect message and, foreach suspect message, suspect message copy data representing a copy ofat least a portion of the suspect message is generated. In oneembodiment, the suspect message copy data is then transferred to one ormore analysis systems for further analysis.

FIG. 4 is a flow chart of a process 400 for virtual asset assistedintrusion detection in a cloud computing environment in accordance withone embodiment. In one embodiment, process 400 for virtual assetassisted intrusion detection in a cloud computing environment begins atENTER OPERATION 401 of FIG. 4 and process flow proceeds to PROVIDE ACLOUD COMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUAL ASSETSOPERATION 403.

In one embodiment, at PROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDINGONE OR MORE VIRTUAL ASSETS OPERATION 403 a cloud computing environmentis provided.

In various embodiments, the cloud computing environment of PROVIDE ACLOUD COMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUAL ASSETSOPERATION 403 can be any form of cloud computing environment, such as,but not limited to, a Virtual Private Cloud, or VPC.

In many cases, a given application or service provided through a cloudcomputing infrastructure may utilize, and interface with, multiple cloudcomputing environments, including multiple VPCs, in the course ofproviding the associated service. As noted above, each cloud computingenvironment includes allocated virtual assets associated with, andcontrolled or used by, the party utilizing the cloud computingenvironment.

As used herein, the term “virtual asset” includes any virtualized entityor resource, and/or part of an actual, or “bare metal” entity requiringaccess to various resources, and types of resources. In variousembodiments, the virtual assets can be, but are not limited to, virtualmachines, virtual servers, and instances implemented in a cloudcomputing environment; databases implemented, or associated with, acloud computing environment, and/or instances implemented in a cloudcomputing environment; services associated with, and/or deliveredthrough, a cloud computing environment; communications systems usedwith, part of, or provided through, a cloud computing environment;and/or any other virtualized assets and/or sub-systems of “bare metal”physical devices such as mobile devices, remote sensors, laptops,desktops, point-of-sale devices, ATMs, electronic voting machines, etc.requiring access to various resources, and/or types of resources,located within a data center, within a cloud computing environment,and/or any other physical or logical location, as discussed herein,and/or as known/available in the art at the time of filing, and/or asdeveloped/made available after the time of filing.

In one embodiment, virtual asset creation data is generated through avirtual asset creation system such as a virtual asset template throughwhich the creator of a virtual asset can generate operational logic andassign resources and attributes to the virtual assets to be instantiatedin a cloud computing environment, such as a virtual private cloudcomputing environment.

In one embodiment, once a cloud computing environment is provided atPROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUALASSETS OPERATION 403, process flow proceeds to PROVIDE ONE OR MORE OFTHE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE ORMORE VIRTUAL ASSETS INTO INTRUSION DETECTION CAPABLE VIRTUAL ASSETSOPERATION 405.

In one embodiment, at PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS ATRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETSINTO INTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 405 a networkcommunications device is provided for each cloud computing environmentof PROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUALASSETS OPERATION 403.

In various embodiments, the network communications devices of PROVIDEONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TOTRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO INTRUSION DETECTIONCAPABLE VIRTUAL ASSETS OPERATION 405 provided for the cloud computingenvironments of PROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDING ONE ORMORE VIRTUAL ASSETS OPERATION 403 include, but are not limited to, oneor more of a switching system, such as a network switch; a router; aborder router; any gateway system; a firewall system; a load balancingsystem; a hypervisor; or any communication, relay, or routing system, asdiscussed herein, and/or as known in the art at the time of filing,and/or as developed after the time of filing, through which messagetraffic on a network communications channel to, or from, an externalnetwork, such as the Internet, is relayed, and/or routed, to one or morevirtual assets in a cloud computing environment.

In one embodiment, incoming message traffic sent to one or more of thevirtual assets associated with a given cloud computing environment ofPROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUALASSETS OPERATION 403 from an origin external to the cloud computingenvironment, such as the Internet, is relayed through the networkcommunications device for that cloud computing environment of PROVIDEONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TOTRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO INTRUSION DETECTIONCAPABLE VIRTUAL ASSETS OPERATION 405.

In one embodiment, the incoming message traffic is relayed through thenetwork communications device of PROVIDE ONE OR MORE OF THE VIRTUALASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUALASSETS INTO INTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 405 viaat least one communications channel, e.g., a network communicationschannel, herein also referred to as a first communications channel.

As noted above, in various embodiments, the incoming message trafficfrom the virtual assets associated with a given cloud computingenvironment of PROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDING ONE ORMORE VIRTUAL ASSETS OPERATION 403 are susceptible to the introduction ofmalware and, in particular, intrusion related malware.

As also noted above, the fact that malware can be introduced into thecloud computing environments of PROVIDE A CLOUD COMPUTING ENVIRONMENTINCLUDING ONE OR MORE VIRTUAL ASSETS OPERATION 403 is a long standingproblem. Consequently, the detection of malware intrusion is animportant part of making the cloud computing environments of PROVIDE ACLOUD COMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUAL ASSETSOPERATION 403 more secure. However, as also noted above, a given cloudcomputing environment, and/or virtual private cloud computingenvironment, can include hundreds, thousands, or even millions, ofvirtual assets, owned or used by hundreds, thousands, or even millions,of parties. Consequently, detecting malware intrusion in a cloudcomputing environment is currently an extremely difficult and resourceintensive task.

To address this issue, in one embodiment, at PROVIDE ONE OR MORE OF THEVIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MOREVIRTUAL ASSETS INTO INTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION405 one or more virtual assets within, and/or assigned to, the cloudcomputing environment of PROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDINGONE OR MORE VIRTUAL ASSETS OPERATION 403 are provided a triggermonitoring system.

In one embodiment, by virtue of the addition of the trigger monitoringsystem logic to one or more of the one or more virtual assets in thecloud computing environment at PROVIDE ONE OR MORE OF THE VIRTUAL ASSETSA TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETSINTO INTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 405 the one ormore virtual assets in the cloud computing environment provided atrigger monitoring system are transformed into intrusion detectioncapable virtual assets for the cloud computing environment.

In various embodiments, the trigger monitoring system of PROVIDE ONE ORMORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THEONE OR MORE VIRTUAL ASSETS INTO INTRUSION DETECTION CAPABLE VIRTUALASSETS OPERATION 405 is a module of software and/or logic implementedin, or on, the one or more virtual assets and capable of monitoring atleast a portion of the message traffic to one or more virtual assetsinstantiated in the cloud computing environment.

In various embodiments, process 400 for virtual asset assisted intrusiondetection in a cloud computing environment is applied to networkcommunications, e.g., message traffic, which is in plain text or isencrypted. Consequently, in some embodiments, the trigger monitoringsystem, and/or the network communications device, and/or the intrusiondetection capable virtual assets of PROVIDE ONE OR MORE OF THE VIRTUALASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUALASSETS INTO INTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 405include a decryption capability to decrypt incoming message traffic aspart of the monitoring and analysis. In other embodiments, a decryptioncapability is provided to decrypt incoming message traffic prior tobeing provided to trigger monitoring system and any monitoring andanalysis.

As discussed below, in some embodiments, the trigger monitoring systemof PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEMTO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO INTRUSION DETECTIONCAPABLE VIRTUAL ASSETS OPERATION 405 allows for analysis policies to beadded, or removed, dynamically based on alerts that are received.

In one embodiment, once one or more virtual assets within, and/orassigned to, the cloud computing environment of PROVIDE A CLOUDCOMPUTING ENVIRONMENT INCLUDING ONE OR MORE VIRTUAL ASSETS OPERATION 403are provided a trigger monitoring system at PROVIDE ONE OR MORE OF THEVIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MOREVIRTUAL ASSETS INTO INTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION405, process flow proceeds to DEFINE ONE OR MORE TRIGGER PARAMETERSOPERATION 407.

In one embodiment, at DEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION407 one or more trigger parameters are defined such that if one or moreof the one or more trigger parameters are detected in a message to avirtual asset, then that message is deemed a suspect message that ispotentially associated with an intrusion attack on the virtual asset,and/or the cloud computing environment.

In various embodiments, the trigger parameters of DEFINE ONE OR MORETRIGGER PARAMETERS OPERATION 407 can be dynamically added, removed,and/or modified to reflect various policies, and/or policy changes madein response to malware alerts. In addition, as discussed below, in oneembodiment, trigger parameters are applied heuristically and new triggerparameters that are discovered by the application of process 400 forvirtual asset assisted intrusion detection in a cloud computingenvironment are added to create a self-learning intrusion detectionsystem.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 407 include, but are notlimited to, the presence of an IP address in a message indicating adesignated suspect origin. In one embodiment, this trigger parameter isused to detect messages coming from a designated suspicious entity thatis suspected of being associated with malware. In various embodiments,the IP addresses associated with designated suspicious entities, and/orthe identity of the entities themselves, is provided by one or morethird parties via alerts or other mechanisms.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 407 include, but are notlimited to, the presence of an IP address in a message indicating adesignated suspect geographical region. In one embodiment, this triggerparameter is used to detect messages coming from geographical locationsthat are known to be associated with malware. In various embodiments,the geographical locations known to be associated with malware areprovided by the one or more third parties via alerts or othermechanisms.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 407 include, but are notlimited to, the presence of an IP address in a message indicating anorigin that is not included on a list of authorized, or expected,origins of messages transmitted to the virtual assets. In oneembodiment, this trigger parameter is used to detect message trafficthat would not be expected to be received in the normal course ofoperation of the virtual assets according to their operational mission.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 407 include, but are notlimited to, the presence of an IP address in a message indicating ageographical location that is not included on a list of authorized, orexpected, geographical locations to be associated with messages to betransmitted to the virtual assets. In one embodiment, this triggerparameter is used to detect message traffic that would not be expectedto be received in the normal course of operation of the virtual assetsaccording to their operational instructions.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 407 include, but are notlimited to, setting a threshold maximum message size and determiningthat a given message is of a size exceeding the threshold maximummessage size. In one embodiment, this trigger parameter takes advantageof the fact that many forms of malware require message sizes larger thanthose normally associated with a given virtual asset in order to exportthe malware necessary to execute the malicious intent.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 407 include, but are notlimited to, setting a threshold minimum message size and determiningthat a given message is of a size that is less than the thresholdminimum message size. In one embodiment, this trigger is used to detectmessages of a size that is smaller than a message size determined to betypical with respect to a given virtual asset, and that are thereforesuspicious.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 407 include, but are notlimited to, trigger parameters based on frequency analysis of the accesspattern indicating that messages arrive too frequently or tooinfrequently.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 407 include, but are notlimited to, a hash value of at least part of the message data that isnot included in a list of allowed hash values. In one embodiment, thistrigger parameter is used in conjunction with a hash-based analysis ofat least part of a given message being transmitted to a virtual asset.In one embodiment, allowable hash values are defined and then a hash isperformed on at least part of a given message. In one embodiment, if thehash of the portion of the given message does not match any of theallowed hash values, the message is determined to be suspect.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 407 include, but are notlimited to, an MD5 value of the message data that is not included in alist of allowed MD5 values.

MD5 (Message-Digest algorithm five) is a widely used cryptographic hashfunction producing a 128 bit (16 byte) hash value that is typicallyexpressed as a 32 digit hexadecimal number. In one embodiment, the MD5algorithm is applied to at least part of the message data associatedwith a given message and the resulting MD5 value is compared with a listof allowed MD5 values. If the resulting MD5 value does not match any ofthe allowed MD5 values, then the message is considered suspect.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 407 include, but are notlimited to, the specific identity of the sender of the message andadding the ability to have a per-message offline analysis thatdetermines whether to trigger a message as suspect. In one embodiment,the analysis can be in-line or asynchronously off-line and wouldtypically miss an initial or first example of an intrusion message butwould be used for other “like messages” where the criteria for “like” isa trigger parameter that can be dynamically installed in the triggermonitoring system. In addition, as discussed below, in one embodiment,trigger parameters are applied heuristically and new trigger parametersthat are discovered by the application of process 400 for virtual assetassisted intrusion detection in a cloud computing environment are addedto create a self-learning intrusion detection system.

In various embodiments, specific examples of trigger parameters ofDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 407 include, but are notlimited to, the specific identity of the recipient of the message andadding the ability to have a per-message offline analysis thatdetermines whether to trigger a message as suspect. In one embodiment,the analysis can be in-line or asynchronously off-line and wouldtypically miss an initial or first example of an intrusion message butwould be used for other “like messages” where the criteria for “like” isa trigger parameter that can be dynamically installed in the triggermonitoring system. In addition, as discussed below, in one embodiment,trigger parameters are applied heuristically and new trigger parametersthat are discovered by the application of process 400 for virtual assetassisted intrusion detection in a cloud computing environment are addedto create a self-learning intrusion detection system.

In various other embodiments, any other trigger parameter, orcombination of trigger parameters, as discussed herein, and/or as knownin the art at the time of filing, and/or as developed after the time offiling is/are defined at DEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION407. In addition, as discussed below, in one embodiment, triggerparameters are applied heuristically and new trigger parameters that arediscovered by the application of process 400 for virtual asset assistedintrusion detection in a cloud computing environment are added to createa self-learning intrusion detection system.

In one embodiment, once one or more trigger parameters are defined atDEFINE ONE OR MORE TRIGGER PARAMETERS OPERATION 407, process flowproceeds to GENERATE TRIGGER DATA REPRESENTING THE TRIGGER PARAMETERSOPERATION 409.

In one embodiment, at GENERATE TRIGGER DATA REPRESENTING THE TRIGGERPARAMETERS OPERATION 409 machine-readable trigger data is generatedrepresenting the trigger parameters of DEFINE ONE OR MORE TRIGGERPARAMETERS OPERATION 407.

In one embodiment, once machine-readable trigger data is generatedrepresenting the trigger parameters of DEFINE ONE OR MORE TRIGGERPARAMETERS OPERATION 407 at GENERATE TRIGGER DATA REPRESENTING THETRIGGER PARAMETERS OPERATION 409, process flow proceeds PROVIDE THETRIGGER DATA TO THE TRIGGER MONITORING SYSTEMS OF THE INTRUSIONDETECTION CAPABLE VIRTUAL ASSETS OPERATION 411.

In one embodiment, at PROVIDE THE TRIGGER DATA TO THE TRIGGER MONITORINGSYSTEMS OF THE INTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 411at least part of the trigger data of GENERATE TRIGGER DATA REPRESENTINGTHE TRIGGER PARAMETERS OPERATION 409 is provided to the triggermonitoring systems of PROVIDE A NETWORK COMMUNICATIONS DEVICE FORRELAYING MESSAGE TRAFFIC SENT TO EACH OF THE VIRTUAL ASSETS OPERATION405.

In one embodiment, once at least part of the trigger data of GENERATETRIGGER DATA REPRESENTING THE TRIGGER PARAMETERS OPERATION 409 isprovided to the trigger monitoring systems of PROVIDE A NETWORKCOMMUNICATIONS DEVICE FOR RELAYING MESSAGE TRAFFIC SENT TO EACH OF THEVIRTUAL ASSETS OPERATION 405 at PROVIDE THE TRIGGER DATA TO THE TRIGGERMONITORING SYSTEMS OF THE INTRUSION DETECTION CAPABLE VIRTUAL ASSETSOPERATION 411, process flow proceeds to USE THE TRIGGER MONITORINGSYSTEMS AND THE TRIGGER DATA TO MONITOR AT LEAST A PORTION OF THEMESSAGE TRAFFIC SENT TO EACH OF THE INTRUSION DETECTION CAPABLE VIRTUALASSETS TO DETECT ANY MESSAGE INCLUDING ONE OR MORE OF THE TRIGGERPARAMETERS OPERATION 413.

In one embodiment, at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGERDATA TO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT TO EACHOF THE INTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 413 thetrigger data of GENERATE TRIGGER DATA REPRESENTING THE TRIGGERPARAMETERS OPERATION 409 and the trigger monitoring system of PROVIDEONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TOTRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO INTRUSION DETECTIONCAPABLE VIRTUAL ASSETS OPERATION 405 are used to monitor at least partof the message data associated with at least some of the intrusiondetection capable virtual assets of PROVIDE ONE OR MORE OF THE VIRTUALASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUALASSETS INTO INTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 405.

In one embodiment, at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGERDATA TO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT TO EACHOF THE INTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 413 the atleast part of the message data associated with at least some of themessage traffic to the intrusion detection capable virtual assets isdecrypted by the decryption capability associated with the triggermonitoring system of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGERMONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTOINTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 405 before thetrigger data of GENERATE TRIGGER DATA REPRESENTING THE TRIGGERPARAMETERS OPERATION 409 and the trigger monitoring system of PROVIDEONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TOTRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO INTRUSION DETECTIONCAPABLE VIRTUAL ASSETS OPERATION 405 are used to monitor at least partof the message data associated with at least some of the message trafficto the intrusion detection capable virtual assets of PROVIDE ONE OR MOREOF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONEOR MORE VIRTUAL ASSETS INTO INTRUSION DETECTION CAPABLE VIRTUAL ASSETSOPERATION 405.

In one embodiment, at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGERDATA TO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT TO EACHOF THE INTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 413 a samplepart of the message data associated with at least some of the messagetraffic to at least some of the intrusion detection capable virtualassets of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORINGSYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO INTRUSIONDETECTION CAPABLE VIRTUAL ASSETS OPERATION 405 is monitored to detectone or more of the one or more trigger parameters within the messagedata.

In one embodiment, at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGERDATA TO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT TO EACHOF THE INTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 413 all of themessage data to at least some of the intrusion detection capable virtualassets of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGER MONITORINGSYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTO INTRUSIONDETECTION CAPABLE VIRTUAL ASSETS OPERATION 405 is monitored to detectone or more of the one or more trigger parameters within the messagedata.

In one embodiment, at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGERDATA TO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT TO EACHOF THE INTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 413 at leastpart of the message data from all of the intrusion detection capablevirtual assets of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGERMONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTOINTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 405 is monitored todetect one or more of the one or more trigger parameters within themessage data.

In one embodiment, at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGERDATA TO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT TO EACHOF THE INTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 413 all of themessage data associated with all of the intrusion detection capablevirtual assets of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGERMONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTOINTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 405 is monitored todetect one or more of the one or more trigger parameters within themessage data.

In one embodiment, the analysis of USE THE TRIGGER MONITORING SYSTEMSAND THE TRIGGER DATA TO MONITOR AT LEAST A PORTION OF THE MESSAGETRAFFIC SENT TO EACH OF THE INTRUSION DETECTION CAPABLE VIRTUAL ASSETSTO DETECT ANY MESSAGE INCLUDING ONE OR MORE OF THE TRIGGER PARAMETERSOPERATION 413 is performed by the trigger monitoring systems in-line, orasynchronously off-line, on a per-message basis. Consequently, in someembodiments, an initial or first example of an intrusion message ispassed through a given intrusion detection capable virtual asset butwould be used to stop other “like messages” where the criteria for“like” is a trigger parameter that can be dynamically installed in thetrigger monitoring system.

In addition, in one embodiment, trigger parameters are appliedheuristically at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGER DATATO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT TO EACH OF THEINTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 413 and newtrigger parameters that are discovered by the application of process 400for virtual asset assisted intrusion detection in a cloud computingenvironment are added to create a self-learning intrusion detectionsystem.

In one embodiment, once the trigger data of GENERATE TRIGGER DATAREPRESENTING THE TRIGGER PARAMETERS OPERATION 409 and the triggermonitoring system of PROVIDE ONE OR MORE OF THE VIRTUAL ASSETS A TRIGGERMONITORING SYSTEM TO TRANSFORM THE ONE OR MORE VIRTUAL ASSETS INTOINTRUSION DETECTION CAPABLE VIRTUAL ASSETS OPERATION 405 are used tomonitor at least part of the message data associated with at least someof the intrusion detection capable virtual assets of PROVIDE ONE OR MOREOF THE VIRTUAL ASSETS A TRIGGER MONITORING SYSTEM TO TRANSFORM THE ONEOR MORE VIRTUAL ASSETS INTO INTRUSION DETECTION CAPABLE VIRTUAL ASSETSOPERATION 405 at USE THE TRIGGER MONITORING SYSTEMS AND THE TRIGGER DATATO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT TO EACH OF THEINTRUSION DETECTION CAPABLE VIRTUAL ASSETS TO DETECT ANY MESSAGEINCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS OPERATION 413, processflow proceeds to CLASSIFY ANY DETECTED MESSAGE INCLUDING ONE OR MORE OFTHE TRIGGER PARAMETERS AS A POTENTIAL SECURITY THREAT OPERATION 415.

In one embodiment, at CLASSIFY ANY DETECTED MESSAGE INCLUDING ONE ORMORE OF THE TRIGGER PARAMETERS AS A POTENTIAL SECURITY THREAT OPERATION415, if one or more of the one or more trigger parameters of DEFINE ONEOR MORE TRIGGER PARAMETERS OPERATION 407 is detected within the messagedata associated with a given message, the classification data associatedwith that message is transformed into classification data indicatingthat the detected message including one or more of the one or moretrigger parameters is a suspect message.

In one embodiment, once the classification data associated with messageshaving one or more of the one or more trigger parameters of DEFINE ONEOR MORE TRIGGER PARAMETERS OPERATION 407 is transformed intoclassification data indicating that the detected message including oneor more of the one or more trigger parameters is a suspect message atCLASSIFY ANY DETECTED MESSAGE INCLUDING ONE OR MORE OF THE TRIGGERPARAMETERS AS A POTENTIAL SECURITY THREAT OPERATION 415, process flowproceeds to ASSIGN A THREAT SCORE TO THE SUSPECT MESSAGE AT LEASTPARTIALLY BASED ON A POTENTIAL IMPACT OF THE SUSPECT MESSAGE'S POTENTIALSECURITY THREAT ON THE INTRUSION DETECTION CAPABLE VIRTUAL ASSETOPERATION 417.

In one embodiment, at ASSIGN A THREAT SCORE TO THE SUSPECT MESSAGE ATLEAST PARTIALLY BASED ON A POTENTIAL IMPACT OF THE SUSPECT MESSAGE'SPOTENTIAL SECURITY THREAT ON THE INTRUSION DETECTION CAPABLE VIRTUALASSET OPERATION 417, a threat score is assigned to the suspect messagebased, at least partially, on a potential impact of the suspectmessage's potential security threat on the intrusion detection capablevirtual asset.

For example, if the potential security threat can compromise financialdata, e.g., credit card information of users, the threat score will behigher than if the potential security threats cause minor decreases innetwork connectivity speeds, according to one embodiment. To determinethe potential impact of the potential security threat, the processevaluates the context of the potential security threat. In other words,the process evaluates the characteristics of the intrusion detectioncapable virtual asset, the type of threat, the likelihood of success ofthe threat, and the like.

In one embodiment, a threat score is assigned to a suspect message basedon the relative impact of a potential security threat to the intrusiondetection capable virtual asset. For example, based on the impact of thepotential security threat, a numerical threat score can be assigned tothe suspect message. For example, a threat score of 10 can be assignedto suspect messages having potential security threats with the highestprobability of successful attack and that acquire personal data of usersof the intrusion detection capable virtual asset. A 0 (zero) can beassigned to suspect messages having potential security threats with thelowest probability of successful attack and/or that are likely to have anegligible effect on the performance of the intrusion detection capablevirtual asset, according to one embodiment. Various factors, such asasset configuration, number of subscribers, security features developedinto the intrusion detection capable virtual asset, notification of newsecurity threats or external risks, or input from a third partyvulnerability scanner, can provide context while assessing a potentialsecurity threat and assigning a threat score. In some embodiments, thethreat scores range between 0-10. In other embodiments, the threatscores range between 0 and 100. In yet other embodiments, the threatscores include values, such as, “LOW,” “MEDIUM,” and “HIGH.” In oneembodiment, the threat scores can include color coordinating so thathigh priority potential security threats are red, low priority potentialsecurity threats are orange, and the absence of potential securitythreats is indicated with green. As those of skill in the art willappreciate, other scoring ranges or values can be used while assigning athreat score to a suspect message having a potential security threat,according to various embodiments.

In one embodiment, once a threat score is assigned to the suspectmessage at ASSIGN A THREAT SCORE TO THE SUSPECT MESSAGE AT LEASTPARTIALLY BASED ON A POTENTIAL IMPACT OF THE SUSPECT MESSAGE'S POTENTIALSECURITY THREAT ON THE INTRUSION DETECTION CAPABLE VIRTUAL ASSETOPERATION 417, process flow proceeds to PROVIDE THE THREAT SCORE TO THEINTRUSION DETECTION CAPABLE VIRTUAL ASSET TO ENABLE THE INTRUSIONDETECTION CAPABLE VIRTUAL ASSET TO SECURE AGAINST THE POTENTIAL SECURITYTHREAT OPERATION 419.

In one embodiment, at PROVIDE THE THREAT SCORE TO THE INTRUSIONDETECTION CAPABLE VIRTUAL ASSET TO ENABLE THE INTRUSION DETECTIONCAPABLE VIRTUAL ASSET TO SECURE AGAINST THE POTENTIAL SECURITY THREATOPERATION 419, the threat score is provided to the intrusion detectioncapable virtual asset to enable the intrusion detection capable virtualasset to secure against the potential security threat.

In some embodiments, threat scores associated with suspect messages areprovided to the intrusion detection capable virtual assets on a periodicbasis in digests, rather than in real time. In some embodiments, threatscores between 0 and 5 are periodically provided to the intrusiondetection capable virtual assets, e.g., on a weekly, semi-monthly, ormonthly basis. In one embodiment, higher threat scores, e.g. threatscores of between 8 and 10, for example, are immediately provided to theintrusion detection capable virtual assets. In one embodiment, threatscores are provided to the intrusion detection capable virtual assetsaccording to the computing resources and human resources available.

The threat scores are provided to the intrusion detection capablevirtual assets for consideration and/or remedial action, according toone embodiment. In some embodiments, one or more identifiers, e.g., anIP address, involved in the potential security threat are provided tothe intrusion detection capable virtual assets to allow the intrusiondetection capable virtual assets to block future communicationsassociated with the suspect message.

In one embodiment, the intrusion detection capable virtual asset securesagainst the potential security threat by submitting the security threatto disciplinary authorities to track down and punish the author(s) ofthe security threat. In other embodiments, the intrusion detectioncapable virtual asset secures against the potential security threat byblocking access of one or more computing systems to the intrusiondetection capable virtual asset.

In one embodiment, once the threat score is provided to the intrusiondetection capable virtual asset at PROVIDE THE THREAT SCORE TO THEINTRUSION DETECTION CAPABLE VIRTUAL ASSET TO ENABLE THE INTRUSIONDETECTION CAPABLE VIRTUAL ASSET TO SECURE AGAINST THE POTENTIAL SECURITYTHREAT OPERATION 419, process flow proceeds to FOR EACH SUSPECT MESSAGEGENERATE SUSPECT MESSAGE COPY DATA REPRESENTING A COPY OF AT LEAST APORTION OF THE SUSPECT MESSAGE OPERATION 421.

In one embodiment, the detected suspect messages of CLASSIFY ANYDETECTED MESSAGE INCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS AS APOTENTIAL SECURITY THREAT OPERATION 415 are temporarily permitted to betransmitted to the virtual assets through the network communicationschannel with minimal delay.

In one embodiment, this transmission is permitted in order to avoidsignificantly disrupting or delaying the transmission of messageswithout further evidence that the suspect messages are indeed malicious.However, in one embodiment, at FOR EACH SUSPECT MESSAGE GENERATE SUSPECTMESSAGE COPY DATA REPRESENTING A COPY OF AT LEAST A PORTION OF THESUSPECT MESSAGE OPERATION 421, for each detected suspect message ofCLASSIFY ANY DETECTED MESSAGE INCLUDING ONE OR MORE OF THE TRIGGERPARAMETERS AS A POTENTIAL SECURITY THREAT OPERATION 415, suspect messagecopy data is generated representing a copy of at least part of themessage data making up the suspect message.

In one embodiment, for each detected suspect message of CLASSIFY ANYDETECTED MESSAGE INCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS AS APOTENTIAL SECURITY THREAT OPERATION 415, the at least part of themessage data making up the suspect message is decrypted and decryptedsuspect message copy data is generated representing a decrypted copy ofat least part of the message data making up the suspect message at FOREACH SUSPECT MESSAGE GENERATE SUSPECT MESSAGE COPY DATA REPRESENTING ACOPY OF AT LEAST A PORTION OF THE SUSPECT MESSAGE OPERATION 421.

In one embodiment, once suspect message copy data is generatedrepresenting a copy of at least part of the message data making up thesuspect message at FOR EACH SUSPECT MESSAGE GENERATE SUSPECT MESSAGECOPY DATA REPRESENTING A COPY OF AT LEAST A PORTION OF THE SUSPECTMESSAGE OPERATION 421 for each detected suspect message of CLASSIFY ANYDETECTED MESSAGE INCLUDING ONE OR MORE OF THE TRIGGER PARAMETERS AS APOTENTIAL SECURITY THREAT OPERATION 415, process flow proceeds toTRANSFER THE SUSPECT MESSAGE COPY DATA TO ONE OR MORE ANALYSIS SYSTEMSFOR FURTHER ANALYSIS OPERATION 423.

In one embodiment, at TRANSFER THE SUSPECT MESSAGE COPY DATA TO ONE ORMORE ANALYSIS SYSTEMS FOR FURTHER ANALYSIS OPERATION 423, the suspectmessage copy data of FOR EACH SUSPECT MESSAGE GENERATE SUSPECT MESSAGECOPY DATA REPRESENTING A COPY OF AT LEAST A PORTION OF THE SUSPECTMESSAGE OPERATION 421 is transmitted to one or more analysis systems forfurther analysis in an “off-line” environment.

In one embodiment, at TRANSFER THE SUSPECT MESSAGE COPY DATA TO ONE ORMORE ANALYSIS SYSTEMS FOR FURTHER ANALYSIS OPERATION 423, the suspectmessage copy data of FOR EACH SUSPECT MESSAGE GENERATE SUSPECT MESSAGECOPY DATA REPRESENTING A COPY OF AT LEAST A PORTION OF THE SUSPECTMESSAGE OPERATION 421 is transmitted to the one or more analysis systemsvia a message analysis channel, also referred to herein as a thirdcommunications channel, that is distinct from the network communicationschannel, i.e., the first communications channel through which messagesare transmitted from the virtual assets relayed by the networkcommunications device of PROVIDE A CLOUD COMPUTING ENVIRONMENT INCLUDINGONE OR MORE VIRTUAL ASSETS OPERATION 403. In this way, the transmissionof the suspect message copy data, and the subsequent message dataanalysis, does not affect the operation of the virtual asset, and/or thecloud computing environment, application, service, enterprise, and/orinfrastructure associated with the virtual asset.

In one embodiment, multiple analysis systems are provided at TRANSFERTHE SUSPECT MESSAGE COPY DATA TO ONE OR MORE ANALYSIS SYSTEMS FORFURTHER ANALYSIS OPERATION 423 that are specifically implemented toanalyze specific trigger parameters of DEFINE ONE OR MORE TRIGGERPARAMETERS OPERATION 407.

Consequently, in one embodiment, the particular analysis system to whicha given example of suspect message data is transmitted at TRANSFER THESUSPECT MESSAGE COPY DATA TO ONE OR MORE ANALYSIS SYSTEMS FOR FURTHERANALYSIS OPERATION 423 is determined, at least in part, by the specifictrigger parameter detected in the suspect message at USE THE TRIGGERMONITORING SYSTEM AND THE TRIGGER DATA TO MONITOR AT LEAST A PORTION OFTHE MESSAGE TRAFFIC SENT TO EACH OF THE ONE OR MORE VIRTUAL ASSETS TODETECT ANY MESSAGE INCLUDING ONE OR MORE OF THE ONE OR MORE TRIGGERPARAMETERS OPERATION 413 from which the suspect message copy data wasderived at FOR EACH SUSPECT MESSAGE GENERATE SUSPECT MESSAGE COPY DATAREPRESENTING A COPY OF AT LEAST A PORTION OF THE SUSPECT MESSAGEOPERATION 421.

In one embodiment, if, as a result of the analysis of the suspectmessage copy data by one or more of the analysis systems at TRANSFER THESUSPECT MESSAGE COPY DATA TO ONE OR MORE ANALYSIS SYSTEMS FOR FURTHERANALYSIS OPERATION 423, it is determined that the suspect message isindeed associated with an intrusion attack, one or more systems,entities, and/or parties, are alerted to the situation so thatappropriate protective action can be taken.

In one embodiment, if, as a result of the analysis of the suspectmessage copy data by one or more of the analysis systems at TRANSFER THESUSPECT MESSAGE COPY DATA TO ONE OR MORE ANALYSIS SYSTEMS FOR FURTHERANALYSIS OPERATION 423, it is determined that the suspect message isindeed associated with an intrusion attack, one or more protectiveactions are automatically taken to prevent further infection of thevirtual assets, and/or other virtual assets, and/or the cloud computingenvironment, application, service, infrastructure, or computingenvironment, associated with the now identified infected virtual asset.

In various embodiments, the protective actions taken can include, butare not limited to, isolating the virtual asset such that the virtualasset can still continue to operate, but in total isolation of all othervirtual assets; partially isolating the virtual asset such that thevirtual asset is allowed to connect to some very specific virtualassets, but has most of its communication channels blocked; “killing” orterminating the virtual asset; repairing the virtual asset by re-loadingthe compromised sub-components of the virtual asset; and/or any otherprotective actions, or combination of protective actions, discussedherein, and/or as known in the art at the time of filing, and/or asdeveloped, or become known, after the time of filing.

In addition, in one embodiment, trigger parameters are appliedheuristically at USE THE TRIGGER MONITORING SYSTEM AND THE TRIGGER DATATO MONITOR AT LEAST A PORTION OF THE MESSAGE TRAFFIC SENT TO EACH OF THEONE OR MORE VIRTUAL ASSETS TO DETECT ANY MESSAGE INCLUDING ONE OR MOREOF THE ONE OR MORE TRIGGER PARAMETERS OPERATION 413 and if, as a resultof the analysis of the suspect message copy data by one or more of theanalysis systems at TRANSFER THE SUSPECT MESSAGE COPY DATA TO ONE ORMORE ANALYSIS SYSTEMS FOR FURTHER ANALYSIS OPERATION 423, it isdetermined that the suspect message is indeed associated with anintrusion attack, new trigger parameters that are thereby discovered bythe application of process 400 for virtual asset assisted intrusiondetection in a cloud computing environment are added at to create aself-learning intrusion detection system.

In one embodiment, once the suspect message copy data of FOR EACHSUSPECT MESSAGE GENERATE SUSPECT MESSAGE COPY DATA REPRESENTING A COPYOF AT LEAST A PORTION OF THE SUSPECT MESSAGE OPERATION 421 istransmitted to one or more analysis systems for further analysis in an“off-line” environment at TRANSFER THE SUSPECT MESSAGE COPY DATA TO ONEOR MORE ANALYSIS SYSTEMS FOR FURTHER ANALYSIS OPERATION 423, processflow proceeds to EXIT OPERATION 430.

In one embodiment, at EXIT OPERATION 430 process 400 for virtual assetassisted intrusion detection in a cloud computing environment is exitedto await new data.

Using process 400 for virtual asset assisted intrusion detection in acloud computing environment discussed above, intrusion attacks can bedetected using largely existing cloud computing environmentinfrastructure, such as modified virtual assets with added triggermonitoring systems; without the need for devoting extensive and/orspecialized resources. Consequently, using process 400 for virtual assetassisted intrusion detection in a cloud computing environment, intrusionevents can be efficiently and effectively detected; thereby makingdistributed computing environments, such as cloud computingenvironments, more secure.

As previously discussed, in addition to extrusion and intrusioncapabilities for which virtual assets depicted and described herein maybe configured, in various embodiments, further disclosure is maderegarding virtual assets having self-monitoring and self-reportingcharacteristics and function. As one of ordinary skill will readilyappreciate, virtual assets may be configured to perform any or all ofthe features and process operations described herein.

In one embodiment, self-monitoring and self-reporting virtual assets,and/or self-monitoring, self-reporting, and self-repairing virtualassets, are instantiated to include at least the virtual assetself-monitoring logic, the virtual asset self-reporting logic, and thevirtual asset self-reporting communications logic, using aself-monitoring, self-reporting, and self-repairing virtual assetcreation template.

FIG. 5 shows a simplified block diagram of a self-monitoring,self-reporting, and self-repairing virtual asset creation template 500.As seen in FIG. 5, in one embodiment, self-monitoring, self-reporting,and self-repairing virtual asset creation template 500 includes primaryvirtual asset logic and data 501.

In one embodiment, primary virtual asset logic and data 501 includesprimary virtual asset logic and data, and instructions associated withthe self-monitoring, self-reporting, and self-repairing virtual assetitself, and/or the normal functions and operations of theself-monitoring, self-reporting, and self-repairing virtual asset,and/or the operating environment of the self-monitoring, self-reporting,and self-repairing virtual asset, such as a cloud computing environmentand/or one or more management systems for the cloud computingenvironment.

As specific illustrative examples, in various embodiments, primaryvirtual asset logic and data 501 includes, but is not limited to, one ormore of, data indicating the self-monitoring, self-reporting, andself-repairing virtual asset's identification; data indicating theregion associated with the self-monitoring, self-reporting, andself-repairing virtual asset; data indicating the availability zoneassociated with the self-monitoring, self-reporting, and self-repairingvirtual asset; data representing and/or indicating software modules andcode residing within, or assigned to, the self-monitoring,self-reporting, and self-repairing virtual asset; data indicating anumber of software modules residing within, or associated with, theself-monitoring, self-reporting, and self-repairing virtual asset; datarepresenting or indicating files and/or file names residing within, orassigned to, the self-monitoring, self-reporting, and self-repairingvirtual asset; data representing and/or indicating the exactconfiguration of the self-monitoring, self-reporting, and self-repairingvirtual asset; data indicating a boot sequence for the self-monitoring,self-reporting, and self-repairing virtual asset; any data provided by ahypervisor or virtualization layer associated with the self-monitoring,self-reporting, and self-repairing virtual asset; any data provided froma cloud control plane associated with the self-monitoring,self-reporting, and self-repairing virtual asset; any data provided byany management system associated with the computing environment of theself-monitoring, self-reporting, and self-repairing virtual asset;communications and data transfer logic associated with theself-monitoring, self-reporting, and self-repairing virtual asset, suchas logic and instructions for providing “normal” communications channelsand data transfer mechanisms to be used by self-monitoring,self-reporting, and self-repairing virtual asset once theself-monitoring, self-reporting, and self-repairing virtual asset isinstantiated, and/or deployed; and/or any combination of “inside” or“normal” operational virtual asset logic and data as discussed herein,and/or as known in the art at the time of filing, and/or as developedafter the time of filing.

In one embodiment, using at least part of primary virtual asset logicand data 501, a self-monitoring, self-reporting, and self-repairingvirtual asset can be instantiated, or launched, in a computingenvironment. In one embodiment, as a specific illustrative example,self-monitoring, self-reporting, and self-repairing virtual asset is aself-monitoring, self-reporting, and self-repairing virtual machine, orself-monitoring, self-reporting, and self-repairing virtual serverinstance, to be launched in a cloud computing environment.

In one embodiment, self-monitoring, self-reporting, and self-repairingvirtual asset creation template 500 includes virtual assetself-monitoring logic 536.

In one embodiment, self-monitoring, self-reporting, and self-repairingvirtual asset creation template 500 includes virtual assetself-reporting logic 537.

In one embodiment, self-monitoring, self-reporting, and self-repairingvirtual asset creation template 500 includes virtual assetself-reporting communication channel creation logic 538.

In one embodiment, self-monitoring, self-reporting, and self-repairingvirtual asset creation template 500 includes virtual assetself-reporting communication port activation logic 503. In oneembodiment, virtual asset self-reporting communication port activationlogic 503 includes instructions and data for generating and activating aself-reporting communications door in response to detection of a triggerevent by virtual asset self-monitoring logic 536 and instructions fromvirtual asset self-reporting communications channel creation logic 538.

In one embodiment, self-monitoring, self-reporting, and self-repairingvirtual asset creation template 500 includes trigger event reportingdata transfer logic 504.

In one embodiment, self-monitoring, self-reporting, and self-repairingvirtual asset creation template 500 includes responsive actionimplementation data receipt logic 506.

In one embodiment, self-monitoring, self-reporting, and self-repairingvirtual asset creation template 500 includes responsive actionimplementation logic 507.

In one embodiment, self-monitoring, self-reporting, and self-repairingvirtual asset creation template 500 includes virtual assetself-reporting communication port deactivation logic 505. In oneembodiment, virtual asset self-reporting communication port deactivationlogic 505 includes instructions and data for deactivating theself-reporting communications door in response instructions from virtualasset self-reporting communications channel creation logic 538.

Using the methods and systems for providing self-monitoring andself-reporting, and/or self-monitoring, self-reporting, andself-repairing virtual assets, discussed herein, self-monitoring andself-reporting, and/or self-monitoring, self-reporting, andself-repairing virtual assets are provided that can independently andautomatically detect one or more trigger events within theself-monitoring and self-reporting, and/or self-monitoring,self-reporting, and self-repairing virtual assets, generate suspiciousevent reporting data from the self-monitoring and self-reporting, and/orself-monitoring, self-reporting, and self-repairing virtual assets, andprovide the reporting data to a monitoring system external to theself-monitoring and self-reporting, and/or self-monitoring,self-reporting, and self-repairing virtual assets, all without relyingdetection of the suspicious event by entities outside theself-monitoring and self-reporting virtual assets, and/orself-monitoring, self-reporting, and self-repairing virtual assets,and/or normal communications channels.

Therefore, using the self-monitoring and self-reporting, and/orself-monitoring, self-reporting, and self-repairing virtual assets, andthe methods and systems for providing self-monitoring andself-reporting, and/or self-monitoring, self-reporting, andself-repairing virtual assets discussed herein, virtual assets, and thedata processed and stored by virtual assets, are made more secure.

In one embodiment, a self-monitoring and self-reporting virtual asset isinstantiated including virtual asset self-monitoring logic, virtualasset self-reporting logic, and virtual asset self-reportingcommunications channel creation logic.

In one embodiment, when a trigger event is detected in theself-monitoring and self-reporting virtual asset using the virtual assetself-monitoring logic, the self-monitoring and self-reporting virtualasset uses the virtual asset self-reporting logic to generate triggerevent reporting data indicating the detected trigger event.

In one embodiment, the self-monitoring and self-reporting virtual assetthen uses the virtual asset self-reporting communications channelcreation logic to open a self-reporting communications channel betweenthe self-monitoring and self-reporting virtual asset and a virtual assetmonitoring system. In one embodiment, the self-monitoring andself-reporting virtual asset then uses the self-reporting communicationschannel to report the trigger event to the virtual asset monitoringsystem.

FIG. 6 is a flow chart of a process 600 for providing self-monitoringand self-reporting virtual assets in accordance with one embodiment. Inone embodiment, process 600 for providing self-monitoring andself-reporting virtual assets begins at ENTER OPERATION 601 of FIG. 6and process flow proceeds to PROVIDE A VIRTUAL ASSET MONITORING SYSTEMOPERATION 603.

In one embodiment, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEMOPERATION 603, a virtual asset monitoring system is provided.

In one embodiment, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEMOPERATION 603 the virtual asset monitoring system is implemented in afirst computing environment that is distinct from the computingenvironment in which the self-monitoring and self-reporting virtualassets are implemented, operated, and/or instantiated.

In one embodiment, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEMOPERATION 603 the virtual asset monitoring system is implemented, atleast in part, in a data center associated with an application beingimplemented and/or an owner of the self-monitoring and self-reportingvirtual assets.

In various embodiments, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEMOPERATION 603 the virtual asset monitoring system is implemented insoftware, hardware, and/or a combination of software and hardware. Inone embodiment, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION603 the virtual asset monitoring system includes a virtual assetmonitoring module. In one embodiment, at PROVIDE A VIRTUAL ASSETMONITORING SYSTEM OPERATION 603 the virtual asset monitoring module ofthe virtual asset monitoring system includes a trigger event reportingdata receipt module which is used to receive detected trigger event datafrom the self-monitoring and self-reporting virtual assets.

In one embodiment, once a virtual asset monitoring system is provided atPROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403, process flowproceeds to DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHENDETECTED IN A VIRTUAL ASSET OPERATION 605.

In one embodiment, at DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTEDWHEN DETECTED IN A VIRTUAL ASSET OPERATION 605, one or more triggerevents are defined.

In various embodiments, the one or more trigger events defined at DEFINEONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUALASSET OPERATION 605 are events, states, or occurrences, that whendetected in a virtual asset represent a potential securityvulnerability, and/or a deviation from normal virtual asset operation.

In various embodiments, the one or more trigger events defined at DEFINEONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUALASSET OPERATION 605 can include, but are not limited to, one or more of,a network message from a virtual asset directed to a location known tobe associated with malicious entities, i.e., a black-listed destination;the frequency of outgoing network messages changing to a level above adefined threshold level, i.e., the frequency of outgoing networkmessages changing to a level deemed “not normal”; a response to acustomer request being directed to a destination that is not thecustomer location of record; a virtual asset receiving a high-frequencyof login attempts that fail; a size of the parameters sent into avirtual asset being outside a defined “normal” range of sizes forparameters; a size of outgoing network messages being outside a defined“normal” range of sizes of outgoing messages; a total amount of data inany one communication connection of a virtual asset exceeding a definedmaximum normal size of a communication to a customer; a request to avirtual asset coming in from a location known to be associated withmalicious entities, i.e., a black-listed origin location; an internalelapsed time of defined critical operations changing to a time outside adefined range of “normal” values; and/or any other trigger event, orcombination of trigger events, as discussed herein, and/or as known inthe art at the time of filing, and/or as developed/made available afterthe time of filing.

In one embodiment, once one or more trigger events are defined at DEFINEONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUALASSET OPERATION 605, process flow proceeds to GENERATE VIRTUAL ASSETSELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE ORMORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 607.

In one embodiment, at GENERATE VIRTUAL ASSET SELF-MONITORING LOGICREPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTSWITHIN A VIRTUAL ASSET OPERATION 607 virtual asset self-monitoring logicis generated for monitoring the operational logic of a virtual asset anddetecting the one or more defined trigger events of DEFINE ONE OR MORETRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION605.

In one embodiment, the virtual asset self-monitoring logic of GENERATEVIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FORDETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSETOPERATION 607 includes machine-readable code and instructions formonitoring the primary operational logic and data of the virtual assetand detecting the one or more defined trigger events within the virtualasset.

In one embodiment, once virtual asset self-monitoring logic is generatedfor monitoring the operational logic of a virtual asset and detectingthe one or more defined trigger events of DEFINE ONE OR MORE TRIGGEREVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 605 atGENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONSFOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSETOPERATION 607, process flow proceeds to GENERATE VIRTUAL ASSETSELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGEREVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 609.

In one embodiment, at GENERATE VIRTUAL ASSET SELF-REPORTING LOGICREPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATAINDICATING A DETECTED TRIGGER EVENT OPERATION 609, virtual assetself-reporting logic is generated for generating trigger event reportingdata indicating a detected trigger event of DEFINE ONE OR MORE TRIGGEREVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 605 ifone of the one or more trigger events is detected in a virtual asset bythe virtual asset self-monitoring logic of GENERATE VIRTUAL ASSETSELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE ORMORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 607.

In one embodiment, the virtual asset self-reporting logic of GENERATEVIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FORGENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGEREVENT OPERATION 609 includes machine-readable code and instructions forcreating detected trigger event data indicating a detected triggerevent, and/or describing the detected trigger event, and/or generatinglog data representing the detected trigger event.

In one embodiment, once virtual asset self-reporting logic is generatedfor generating trigger event reporting data indicating a detectedtrigger event of DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHENDETECTED IN A VIRTUAL ASSET OPERATION 605 if one of the one or moretrigger events is detected in a virtual asset by the virtual assetself-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGICREPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTSWITHIN A VIRTUAL ASSET OPERATION 607 at GENERATE VIRTUAL ASSETSELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGEREVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 609,process flow proceeds to GENERATE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTINGCOMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 611.

In one embodiment, at GENERATE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTINGCOMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 611, virtual asset self-reportingcommunications channel creation logic is generated for opening aself-reporting communications channel between a virtual asset and thevirtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORINGSYSTEM OPERATION 603 if one of the one or more trigger events of DEFINEONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUALASSET OPERATION 605 is detected in a virtual asset by the virtual assetself-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGICREPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTSWITHIN A VIRTUAL ASSET OPERATION 607.

In one embodiment, the virtual asset self-reporting communicationchannel creation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTINGCOMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 611 includes machine-readable code andinstructions for activating a virtual asset self-reportingcommunications port, or door, pre-deployed, and/or implemented by, thevirtual asset self-reporting communications channel creation logic inthe virtual asset and thereby opening a self-reporting communicationschannel between a virtual asset and the virtual asset monitoring system.

In one embodiment, once virtual asset self-reporting communicationschannel creation logic is generated for opening a self-reportingcommunications channel between a virtual asset and the virtual assetmonitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION603 when one of the one or more trigger events of DEFINE ONE OR MORETRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION605 is detected in a virtual asset by the virtual asset self-monitoringlogic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTINGINSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN AVIRTUAL ASSET OPERATION 607 at GENERATE SELF-REPORTING COMMUNICATIONSCHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING ASELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THEVIRTUAL ASSET MONITORING SYSTEM OPERATION 611, process flow proceeds toINSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDINGTHE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSETSELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC OPERATION 613.

In one embodiment, at INSTANTIATE A SELF-MONITORING AND SELF-REPORTINGVIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THEVIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 613, one or moreself-monitoring and self-reporting virtual assets are instantiated in acomputing environment.

In one embodiment, at INSTANTIATE A SELF-MONITORING AND SELF-REPORTINGVIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THEVIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 613 the one or moreself-monitoring and self-reporting virtual assets are instantiated in asecond computing environment that is distinct from the first computingenvironment in which the virtual asset monitoring system of PROVIDE AVIRTUAL ASSET MONITORING SYSTEM OPERATION 603 is implemented.

In one embodiment, at INSTANTIATE A SELF-MONITORING AND SELF-REPORTINGVIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THEVIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 613 the one or moreself-monitoring and self-reporting virtual assets are instantiated in acloud computing environment that is distinct from a data center in whichthe virtual asset monitoring system of PROVIDE A VIRTUAL ASSETMONITORING SYSTEM OPERATION 603 is implemented.

As noted above, as used herein, the term “virtual asset”, such as usedin the term “self-monitoring and self-reporting virtual asset” includesany virtualized entity or resource, and/or part of an actual, or “baremetal” entity.

In various embodiments, any, or all, of the assets making up a givenproduction environment, the computing systems, and/or computing entitiesdiscussed herein, and/or as known in the art at the time of filing,and/or as developed after the time of filing, can be implemented asvirtual assets, and more particularly as, self-monitoring andself-reporting virtual assets.

As also noted above, virtual assets, including self-monitoring andself-reporting virtual assets are created, or instantiated, using steps,instructions, processes, code, or “recipes” referred to herein as“virtual asset creation templates.” Typically, virtual assets that havethe same, or similar, operational parameters are created using the sameor similar “virtual asset creation templates.”

Examples of virtual asset creation templates include, but are notlimited to, any tool and/or system for creating and managing acollection of related cloud resources. One specific illustrative exampleof such a virtual asset creation template is a cloud formation templatesuch as any of the Amazon Web Service (AWS) cloud formationtools/templates.

Other examples of virtual asset creation templates include, but are notlimited to, any configuration management tool associated with, and/orused to create, virtual assets. One specific illustrative example ofsuch a virtual asset creation template is a cookbook or recipe tool suchas a Chef Recipe or system.

Other examples of virtual asset creation templates include, but are notlimited to, any virtual appliance used to instantiate virtual assets.One specific illustrative example of such a virtual asset creationtemplate is an Amazon Machine Image (AMI).

Other examples of virtual asset creation templates include, but are notlimited to, any appliance, or tool, or system, or framework, used toinstantiate virtual assets as discussed herein, and/or asknown/available in the art at the time of filing, and/or asdeveloped/made available after the time of filing.

In one embodiment, the virtual asset self-monitoring logic of GENERATEVIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FORDETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSETOPERATION 607, the virtual asset self-reporting logic of GENERATEVIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FORGENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGEREVENT OPERATION 609, and the virtual asset self-reporting communicationschannel creation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTINGCOMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 611, are provided to each of the one or moreself-monitoring and self-reporting virtual assets instantiated atINSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDINGTHE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSETSELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC OPERATION 613.

In one embodiment, the virtual asset self-monitoring logic, the virtualasset self-reporting logic, and the virtual asset self-reportingcommunications channel creation logic, are provided to each of the oneor more self-monitoring and self-reporting virtual assets instantiatedin the computing environment at INSTANTIATE A SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORINGLOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 613 using one or moreself-monitoring, self-reporting, and self-repairing virtual assetcreation templates.

In one embodiment, once one or more self-monitoring and self-reportingvirtual assets are instantiated in a computing environment atINSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDINGTHE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSETSELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC OPERATION 613, process flow proceeds to USE THE VIRTUALASSET SELF-MONITORING LOGIC IN THE SELF-MONITORING AND SELF-REPORTINGVIRTUAL ASSET TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET OPERATION 615.

In one embodiment, at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC IN THESELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO DETECT A TRIGGEREVENT IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET OPERATION615, the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSETSELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE ORMORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 607 provided to theone or more self-monitoring and self-reporting virtual assets atINSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDINGTHE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSETSELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC OPERATION 613 is used to monitor and detect any of thedefined trigger events of DEFINE ONE OR MORE TRIGGER EVENTS TO BEREPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 605 within theself-monitoring and self-reporting virtual assets.

In one embodiment, at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC IN THESELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO DETECT A TRIGGEREVENT IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET OPERATION615 the virtual asset self-monitoring logic is used to monitor anddetect any of the defined trigger events within the self-monitoring andself-reporting virtual assets by monitoring primary virtual asset logicand data used by the self-monitoring and self-reporting virtual assetsin the course of their normal operations and the performance of theirassigned functions.

In one embodiment, once the virtual asset self-monitoring logic ofGENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONSFOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSETOPERATION 607 provided to the one or more self-monitoring andself-reporting virtual assets at INSTANTIATE A SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORINGLOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 613 is used to monitorand detect any of the defined trigger events of DEFINE ONE OR MORETRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION605 within the self-monitoring and self-reporting virtual assets at USETHE VIRTUAL ASSET SELF-MONITORING LOGIC IN THE SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET TO DETECT A TRIGGER EVENT IN THESELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET OPERATION 615, processflow proceeds to USE THE VIRTUAL ASSET SELF-REPORTING LOGIC IN THESELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE TRIGGEREVENT REPORTING DATA OPERATION 617.

In one embodiment, if one of the defined trigger events is detectedwithin one of the self-monitoring and self-reporting virtual assets bythe virtual asset self-monitoring logic at USE THE VIRTUAL ASSETSELF-MONITORING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUALASSET TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET OPERATION 615, then at USE THE VIRTUALASSET SELF-REPORTING LOGIC IN THE SELF-MONITORING AND SELF-REPORTINGVIRTUAL ASSET TO GENERATE TRIGGER EVENT REPORTING DATA OPERATION 617detected trigger event data associated with, describing, or representinglog data associated with, the detected trigger event is generated by thevirtual asset self-reporting logic of GENERATE VIRTUAL ASSETSELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGEREVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 609provided to the affected self-monitoring and self-reporting virtualasset at INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSETINCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSETSELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC OPERATION 613.

In one embodiment, once detected trigger event data associated with,describing, or representing log data associated with, the detectedtrigger event is generated by the virtual asset self-reporting logicprovided to the affected self-monitoring and self-reporting at USE THEVIRTUAL ASSET SELF-REPORTING LOGIC IN THE SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET TO GENERATE TRIGGER EVENT REPORTING DATAOPERATION 617, process flow proceeds to USE THE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC IN THE SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET TO GENERATE A SELF-REPORTING COMMUNICATIONSCHANNEL BETWEEN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET ANDTHE VIRTUAL ASSET MONITORING SYSTEM OPERATION 619.

In one embodiment, once a defined trigger event is detected within theself-monitoring and self-reporting virtual asset by the virtual assetself-monitoring logic at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC INTHE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO DETECT A TRIGGEREVENT IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET OPERATION615, at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC INTHE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE ASELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEMOPERATION 619 the virtual asset self-reporting communications channelcreation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTINGCOMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 611 provided to the self-monitoring andself-reporting virtual asset at INSTANTIATE A SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORINGLOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 613, is used to generatea self-reporting communications channel between the self-monitoring andself-reporting virtual asset and the virtual asset monitoring system ofPROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 603.

As noted above, in one embodiment, the virtual asset self-reportingcommunications channel creation logic of GENERATE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOROPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSETAND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 611 generates aself-reporting communications channel at USE THE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC IN THE SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET TO GENERATE A SELF-REPORTING COMMUNICATIONSCHANNEL BETWEEN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET ANDTHE VIRTUAL ASSET MONITORING SYSTEM OPERATION 619 by activating aself-reporting virtual asset self-reporting communications portpre-deployed, and/or implemented by, the virtual asset self-reportingcommunications channel creation logic.

In one embodiment, the self-reporting communications channel generatedby the virtual asset self-reporting communications channel creationlogic at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC INTHE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE ASELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEMOPERATION 619 is a communications channel distinct, and separate from,the various other “normal” communications channels utilized by theself-monitoring and self-reporting virtual assets and/or other assetswithin the computing environment, and/or production environment,associated with the self-monitoring and self-reporting virtual assets.

Consequently, in one embodiment, the self-reporting communicationschannel generated by the virtual asset self-reporting communicationschannel creation logic at USE THE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSETTO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THESELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 619 is not subject to manipulation, and/ortermination, by a malicious party that may have taken control of theself-monitoring and self-reporting virtual asset. In addition, theself-reporting communications channel generated by the virtual assetself-reporting communications channel creation logic is not dependent onsecurity policy implementation systems and entities outside of theself-monitoring and self-reporting virtual asset, other than the virtualasset monitoring system.

In one embodiment, once the virtual asset self-reporting communicationschannel creation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTINGCOMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 611 provided to the self-monitoring andself-reporting virtual asset at INSTANTIATE A SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORINGLOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 613, is used to generatea self-reporting communications channel between the self-monitoring andself-reporting virtual asset and the virtual asset monitoring system ofPROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 603 at USE THESELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC IN THESELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE ASELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEMOPERATION 619, process flow proceeds to USE THE SELF-REPORTINGCOMMUNICATIONS CHANNEL TO TRANSFER THE TRIGGER EVENT REPORTING DATA FROMTHE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO THE VIRTUALASSET MONITORING SYSTEM OPERATION 621.

In one embodiment, at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL TOTRANSFER THE TRIGGER EVENT REPORTING DATA FROM THE SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET TO THE VIRTUAL ASSET MONITORING SYSTEMOPERATION 621 the detected trigger event data of USE THE VIRTUAL ASSETSELF-REPORTING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUALASSET TO GENERATE TRIGGER EVENT REPORTING DATA OPERATION 617 istransferred from the self-monitoring and self-reporting virtual asset tothe virtual asset monitoring system of PROVIDE A VIRTUAL ASSETMONITORING SYSTEM OPERATION 603 using the virtual asset self-reportingcommunications channel generated by the virtual asset self-reportingcommunications channel creation logic at USE THE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC IN THE SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET TO GENERATE A SELF-REPORTING COMMUNICATIONSCHANNEL BETWEEN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET ANDTHE VIRTUAL ASSET MONITORING SYSTEM OPERATION 619.

In one embodiment, once the detected trigger event data of USE THEVIRTUAL ASSET SELF-REPORTING LOGIC IN THE SELF-MONITORING ANDSELF-REPORTING VIRTUAL ASSET TO GENERATE TRIGGER EVENT REPORTING DATAOPERATION 617 is transferred from the self-monitoring and self-reportingvirtual asset to the virtual asset monitoring system of PROVIDE AVIRTUAL ASSET MONITORING SYSTEM OPERATION 603 using the virtual assetself-reporting communications channel generated by the virtual assetself-reporting communications channel creation logic at USE THESELF-REPORTING COMMUNICATIONS CHANNEL TO TRANSFER THE TRIGGER EVENTREPORTING DATA FROM THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSETTO THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 621, process flowproceeds to EXIT OPERATION 630.

In one embodiment, at EXIT OPERATION 630 process 600 for providingself-monitoring and self-reporting virtual assets is exited to await newdata.

Using the self-monitoring and self-reporting virtual assets of process400 for providing self-monitoring and self-reporting virtual assets,self-monitoring and self-reporting virtual assets are provided that canindependently and automatically detect one or more trigger events withinthe self-monitoring and self-reporting virtual assets, generatesuspicious event reporting data from the self-monitoring andself-reporting virtual assets, and provide the reporting data to amonitoring system external to self-monitoring and self-reporting virtualassets, all without relying detection of the suspicious event byentities outside the self-monitoring and self-reporting virtual assetsthemselves, and/or normal communications channels.

Therefore, using the self-monitoring and self-reporting virtual assets,and the methods and systems for providing self-monitoring andself-reporting virtual assets discussed herein, virtual assets, and thedata processed and stored by virtual assets, are made more secure.

In the specific illustrative embodiments discussed above where thedetected trigger event is detected in a self-monitoring andself-reporting virtual asset, once the detected trigger event data istransferred from the self-monitoring and self-reporting virtual asset tothe virtual asset monitoring system, analysis is performed at thevirtual asset monitoring system and appropriate investigative and/orprotective action is taken in response to the detected trigger event.

However, where the detected trigger event is detected in aself-monitoring, self-reporting, and self-repairing virtual asset, oncethe detected trigger event data is transferred from the self-monitoringand self-reporting virtual asset to the virtual asset monitoring system,further analysis and actions are taken automatically.

In one embodiment, a self-monitoring, self-reporting, and self-repairingvirtual asset is instantiated including virtual asset self-monitoringlogic, virtual asset self-reporting logic, and virtual assetself-reporting communications channel creation logic.

In one embodiment, when a trigger event is detected in theself-monitoring, self-reporting, and self-repairing virtual asset usingthe virtual asset self-monitoring logic, the self-monitoring,self-reporting, and self-repairing virtual asset uses the virtual assetself-reporting logic to generate trigger event reporting data indicatingthe detected trigger event.

In one embodiment, the self-monitoring, self-reporting, andself-repairing virtual asset then uses the virtual asset self-reportingcommunications channel creation logic to open a self-reportingcommunications channel between the self-monitoring, self-reporting, andself-repairing virtual asset and a virtual asset monitoring system. Inone embodiment, the self-monitoring, self-reporting, and self-repairingvirtual asset then uses the self-reporting communications channel toreport the trigger event to the virtual asset monitoring system.

In one embodiment, responsive action implementation data representinginstructions for implementing one or more responsive actions to thetrigger event is then generated and sent to the self-monitoring,self-reporting, and self-repairing virtual asset where theself-monitoring, self-reporting, and self-repairing virtual asset usesthe responsive action implementation data to respond to the triggerevent.

FIG. 7 is a flow chart of a process 700 for providing self-monitoring,self-reporting, and self-repairing virtual assets in accordance with oneembodiment. In one embodiment, process 700 for providingself-monitoring, self-reporting, and self-repairing virtual assetsbegins at ENTER OPERATION 701 of FIG. 7 and process flow proceeds toPROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 703.

In one embodiment, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEMOPERATION 703, a virtual asset monitoring system is provided.

In one embodiment, the virtual asset monitoring system of PROVIDE AVIRTUAL ASSET MONITORING SYSTEM OPERATION 703 is implemented in a firstcomputing environment that is distinct from the computing environment inwhich the self-monitoring, self-reporting, and self-repairing virtualassets are implemented, operated, and/or instantiated.

In one embodiment, the virtual asset monitoring system of PROVIDE AVIRTUAL ASSET MONITORING SYSTEM OPERATION 703 is implemented, at leastin part, in a data center associated with the application beingimplemented, and/or an owner of the self-monitoring, self-reporting, andself-repairing virtual assets. In various embodiments, the virtual assetmonitoring system is implemented in software, hardware, and/or acombination of software and hardware.

In one embodiment, the virtual asset monitoring system of PROVIDE AVIRTUAL ASSET MONITORING SYSTEM OPERATION 703 includes a virtual assetmonitoring module and a response action implementation module.

In one embodiment, the virtual asset monitoring module of the virtualasset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEMOPERATION 703 includes a trigger event reporting data receipt modulewhich, as discussed below, is used to receive detected trigger eventdata from the self-monitoring, self-reporting, and self-repairingvirtual assets.

In one embodiment, the responsive action implementation module of thevirtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORINGSYSTEM OPERATION 703 includes the capability to analyze the detectedtrigger event data received from the self-monitoring, self-reporting,and self-repairing virtual assets. In one embodiment, the analysiscapability of the responsive action implementation module takes the formof a mapping module used to map specific detected trigger event data tospecific responsive action data.

In a specific illustrative example, in one embodiment, the responsiveaction implementation module receives the detected trigger event datafrom the trigger event reporting data receipt module and a mappingmodule is used to analyze the detected trigger event data and identifythe detected trigger event. In this specific illustrative example, themapping module then maps the detected trigger event to a specificresponsive action represented and implemented by associated responsiveaction data.

In one embodiment, once a virtual asset monitoring system is provided atPROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 703, process flowproceeds to GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTINGINSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN AVIRTUAL ASSET OPERATION 705.

In one embodiment, at GENERATE VIRTUAL ASSET SELF-MONITORING LOGICREPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTSWITHIN A VIRTUAL ASSET OPERATION 705, one or more trigger events aredefined and virtual asset self-monitoring logic is generated formonitoring the operational logic of a virtual asset and detecting theone or more defined trigger events.

In various embodiments, the one or more trigger events defined atGENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONSFOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSETOPERATION 705 are events, states, or occurrences, that when detected ina virtual asset represent a potential security vulnerability, and/or adeviation from normal virtual asset operation.

In various embodiments, the one or more trigger events defined atGENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONSFOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSETOPERATION 705 can include, but are not limited to, one or more of, anetwork message from a virtual asset directed to a location known to beassociated with malicious entities, i.e., a black-listed destination;the frequency of outgoing network messages changing to a level above adefined threshold level, i.e., the frequency of outgoing networkmessages changing to a level deemed “not normal”; a response to acustomer request being directed to a destination that is not thecustomer location of record; a virtual asset receiving a high-frequencyof login attempts that fail; a size of the parameters sent into avirtual asset being outside a defined “normal” range of sizes forparameters; a size of outgoing network messages being outside a defined“normal” range of sizes of outgoing messages; a total amount of data inany one communication connection of a virtual asset exceeding a definedmaximum normal size of a communication to a customer; a request to avirtual asset coming in from a location known to be associated withmalicious entities, i.e., a black-listed origin location; an internalelapsed time of defined critical operations changing to a time outside adefined range of “normal” values; and/or any other trigger event, orcombination of trigger events, as discussed herein, and/or as known inthe art at the time of filing, and/or as developed/made available afterthe time of filing.

In one embodiment, once one or more trigger events are defined atGENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONSFOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSETOPERATION 705, virtual asset self-monitoring logic is generated formonitoring the operational logic of a virtual asset and detecting theone or more defined trigger events.

In one embodiment, the virtual asset self-monitoring logic of GENERATEVIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FORDETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSETOPERATION 705 includes machine-readable code and instructions formonitoring the operational logic of the virtual asset and detecting theone or more defined trigger events within the virtual asset.

In one embodiment, once one or more trigger events are defined andvirtual asset self-monitoring logic is generated for monitoring theoperational logic of a virtual asset and detecting the one or moredefined trigger events at GENERATE VIRTUAL ASSET SELF-MONITORING LOGICREPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTSWITHIN A VIRTUAL ASSET OPERATION 705, process flow proceeds to GENERATEVIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FORGENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGEREVENT OPERATION 707.

In one embodiment, at GENERATE VIRTUAL ASSET SELF-REPORTING LOGICREPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATAINDICATING A DETECTED TRIGGER EVENT OPERATION 707, virtual assetself-reporting logic is generated for generating trigger event reportingdata indicating a detected trigger event if one of the one or moretrigger events is detected in a virtual asset by the virtual assetself-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGICREPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTSWITHIN A VIRTUAL ASSET OPERATION 705.

In one embodiment, the virtual asset self-reporting logic of GENERATEVIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FORGENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGEREVENT OPERATION 707 includes machine-readable code and instructions forcreating detected trigger event data indicating a detected triggerevent, and/or describing the detected trigger event, and/or generatinglog data representing the detected trigger event.

In one embodiment, once virtual asset self-reporting logic is generatedfor generating trigger event reporting data indicating a detectedtrigger event if one of the one or more trigger events is detected in avirtual asset by the virtual asset self-monitoring logic of GENERATEVIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FORDETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSETOPERATION 705 at GENERATE VIRTUAL ASSET SELF-REPORTING LOGICREPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATAINDICATING A DETECTED TRIGGER EVENT OPERATION 707, process flow proceedsto GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGICREPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONSCHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEMOPERATION 709.

In one embodiment, at GENERATE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTINGCOMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 709, virtual asset self-reportingcommunications channel creation logic is generated for opening aself-reporting communications channel between a virtual asset and thevirtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORINGSYSTEM OPERATION 703 if one of the one or more trigger events isdetected in a virtual asset by the virtual asset self-monitoring logicof GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTINGINSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN AVIRTUAL ASSET OPERATION 705.

In one embodiment, the virtual asset self-reporting communicationchannel creation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTINGCOMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 709 includes machine-readable code andinstructions for activating a self-reporting communications port, ordoor, implemented by the virtual asset self-reporting communicationschannel creation logic in the virtual and thereby opening aself-reporting communications channel between a virtual asset and thevirtual asset monitoring system.

In one embodiment, once virtual asset self-reporting communicationschannel creation logic is generated for opening a self-reportingcommunications channel between a virtual asset and the virtual assetmonitoring system if one of the one or more trigger events is detectedin a virtual asset by the virtual asset self-monitoring logic atGENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGICREPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONSCHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEMOPERATION 709, process flow proceeds to INSTANTIATE A SELF-MONITORING,SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET, INCLUDING THE VIRTUALASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC ANDTHE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 711.

In one embodiment, at INSTANTIATE A SELF-MONITORING, SELF-REPORTING, ANDSELF-REPAIRING VIRTUAL ASSET, INCLUDING THE VIRTUAL ASSETSELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC AND THESELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 711, oneor more self-monitoring, self-reporting, and self-repairing virtualassets, are instantiated in a computing environment.

In one embodiment, the one or more self-monitoring, self-reporting, andself-repairing virtual assets, are instantiated at INSTANTIATE ASELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET,INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSETSELF-REPORTING LOGIC AND THE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC OPERATION 711 in a second computing environment that isdistinct from the first computing environment in which the virtual assetmonitoring system is implemented.

In one embodiment, the one or more self-monitoring, self-reporting, andself-repairing virtual assets, are instantiated at INSTANTIATE ASELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET,INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSETSELF-REPORTING LOGIC AND THE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC OPERATION 711 in a cloud computing environment that isdistinct from a data center in which the virtual asset monitoring systemis implemented.

As noted above, as used herein, the term “virtual asset”, such as usedin the term “self-monitoring, self-reporting, and self-repairing virtualasset” includes any virtualized entity or resource, and/or part of anactual, or “bare metal” entity.

In various embodiments, any, or all, of the assets making up a givenproduction environment, the computing systems, and/or computing entitiesdiscussed herein, and/or as known in the art at the time of filing,and/or as developed after the time of filing, can be implemented asvirtual assets, and more particularly as self-monitoring,self-reporting, and self-repairing virtual assets.

In one embodiment, the virtual asset self-monitoring logic of GENERATEVIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FORDETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSETOPERATION 705, the virtual asset self-reporting logic of GENERATEVIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FORGENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGEREVENT OPERATION 707, and the virtual asset self-reporting communicationschannel creation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTINGCOMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 709, are provided to each of the one or moreself-monitoring, self-reporting, and self-repairing virtual assets ofINSTANTIATE A SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRINGVIRTUAL ASSET, INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THEVIRTUAL ASSET SELF-REPORTING LOGIC AND THE SELF-REPORTING COMMUNICATIONSCHANNEL CREATION LOGIC OPERATION 711.

In one embodiment, at INSTANTIATE A SELF-MONITORING, SELF-REPORTING, ANDSELF-REPAIRING VIRTUAL ASSET, INCLUDING THE VIRTUAL ASSETSELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC AND THESELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 711 thevirtual asset self-monitoring logic, the virtual asset self-reportinglogic, and the virtual asset self-reporting communications channelcreation logic, are provided to each of the one or more self-monitoring,self-reporting, and self-repairing virtual assets, using one or moreself-monitoring, self-reporting, and self-repairing virtual assetcreation templates.

In one embodiment, once one or more self-monitoring, self-reporting, andself-repairing virtual assets, are instantiated in a computingenvironment at INSTANTIATE A SELF-MONITORING, SELF-REPORTING, ANDSELF-REPAIRING VIRTUAL ASSET, INCLUDING THE VIRTUAL ASSETSELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC AND THESELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 711,process flow proceeds to USE THE VIRTUAL ASSET SELF-MONITORING LOGIC TODETECT A TRIGGER EVENT IN THE SELF-MONITORING, SELF-REPORTING, ANDSELF-REPAIRING VIRTUAL ASSET OPERATION 713.

In one embodiment, at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC TODETECT A TRIGGER EVENT IN THE SELF-MONITORING, SELF-REPORTING, ANDSELF-REPAIRING VIRTUAL ASSET OPERATION 713, the virtual assetself-monitoring logic provided to the self-monitoring, self-reporting,and self-repairing virtual assets is used to monitor and detect any ofthe defined trigger events within the self-monitoring, self-reporting,and self-repairing virtual assets.

In one embodiment, at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC TODETECT A TRIGGER EVENT IN THE SELF-MONITORING, SELF-REPORTING, ANDSELF-REPAIRING VIRTUAL ASSET OPERATION 713 the virtual assetself-monitoring logic is used to monitor and detect any of the definedtrigger events within the self-monitoring, self-reporting, andself-repairing virtual assets by monitoring primary virtual asset logicand data used by the self-monitoring, self-reporting, and self-repairingvirtual assets in the course of their normal operations and theperformance of their assigned functions.

In one embodiment, once the virtual asset self-monitoring logic providedto the self-monitoring, self-reporting, and self-repairing virtualassets is used to monitor and detect any of the defined trigger eventswithin the self-monitoring, self-reporting, and self-repairing virtualassets at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC TO DETECT ATRIGGER EVENT IN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRINGVIRTUAL ASSET OPERATION 713, process flow proceeds to USE THE VIRTUALASSET SELF-REPORTING LOGIC TO GENERATE TRIGGER EVENT REPORTING DATAINDICATING THE DETECTED TRIGGER EVENT HAS BEEN DETECTED OPERATION 715.

In one embodiment, if one of the defined trigger events is detectedwithin an affected one of the self-monitoring, self-reporting, andself-repairing virtual assets by the virtual asset self-monitoring logicat USE THE VIRTUAL ASSET SELF-MONITORING LOGIC TO DETECT A TRIGGER EVENTIN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSETOPERATION 713, then, at USE THE VIRTUAL ASSET SELF-REPORTING LOGIC TOGENERATE TRIGGER EVENT REPORTING DATA INDICATING THE DETECTED TRIGGEREVENT HAS BEEN DETECTED OPERATION 715, detected trigger event dataassociated with, describing, or representing log data associated with,the detected trigger event is generated by the virtual assetself-reporting logic provided to the affected self-monitoring,self-reporting, and self-repairing virtual asset.

In one embodiment, once detected trigger event data associated with,describing, or representing log data associated with, the detectedtrigger event is generated by the virtual asset self-reporting logicprovided to the affected self-monitoring, self-reporting, andself-repairing virtual asset at USE THE VIRTUAL ASSET SELF-REPORTINGLOGIC TO GENERATE TRIGGER EVENT REPORTING DATA INDICATING THE DETECTEDTRIGGER EVENT HAS BEEN DETECTED OPERATION 715, process flow proceeds toUSE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATEA SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING,SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 717.

In one embodiment, once a defined trigger event is detected within theself-monitoring, self-reporting, and self-repairing virtual asset by thevirtual asset self-monitoring logic at USE THE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATE A SELF-REPORTINGCOMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING, SELF-REPORTING, ANDSELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEMOPERATION 717, the virtual asset self-reporting communications channelcreation logic provided to the self-monitoring, self-reporting, andself-repairing virtual asset, is used to generate a self-reportingcommunications channel between the self-monitoring, self-reporting, andself-repairing virtual asset and the virtual asset monitoring system.

As noted above, in one embodiment, at USE THE SELF-REPORTINGCOMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATE A SELF-REPORTINGCOMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING, SELF-REPORTING, ANDSELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEMOPERATION 717, the virtual asset self-reporting communications channelcreation logic generates a self-reporting communications channel byactivating a self-reporting virtual asset self-reporting communicationsport pre-deployed, and/or implemented by, the virtual assetself-reporting communications channel creation logic.

In one embodiment, the self-reporting communications channel generatedby the virtual asset self-reporting communications channel creationlogic at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TOGENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THESELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET ANDTHE VIRTUAL ASSET MONITORING SYSTEM OPERATION 717 is a communicationschannel distinct, and separate from, the various other “normal”communications channels utilized by the self-monitoring, self-reporting,and self-repairing virtual assets, and/or other assets within thecomputing environment, and/or production environment, associated withthe self-monitoring, self-reporting, and self-repairing virtual assets.

Consequently, in one embodiment, the self-reporting communicationschannel generated by the virtual asset self-reporting communicationschannel creation logic at USE THE SELF-REPORTING COMMUNICATIONS CHANNELCREATION LOGIC TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNELBETWEEN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUALASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 717 is notsubject to manipulation, and/or termination, by a malicious party thatmay have taken control of the self-monitoring, self-reporting, andself-repairing virtual asset.

In addition, the self-reporting communications channel generated by thevirtual asset self-reporting communications channel creation logic atUSE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATEA SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING,SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 717 is not dependent on security policyimplementation systems and entities outside of the self-monitoring,self-reporting, and self-repairing virtual asset, other than the virtualasset monitoring system.

In one embodiment, once the virtual asset self-reporting communicationschannel creation logic provided to the self-monitoring, self-reporting,and self-repairing virtual asset, is used to generate a self-reportingcommunications channel between the self-monitoring, self-reporting, andself-repairing virtual asset and the virtual asset monitoring system atUSE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATEA SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING,SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 717, process flow proceeds to USE THESELF-REPORTING COMMUNICATIONS CHANNEL TO TRANSFER THE TRIGGER EVENTREPORTING DATA FROM THE SELF-MONITORING, SELF-REPORTING, ANDSELF-REPAIRING VIRTUAL ASSET TO THE VIRTUAL ASSET MONITORING SYSTEMOPERATION 719.

In one embodiment, at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL TOTRANSFER THE TRIGGER EVENT REPORTING DATA FROM THE SELF-MONITORING,SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET TO THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 719, the detected trigger event datagenerated by the virtual asset self-reporting logic at USE THE VIRTUALASSET SELF-REPORTING LOGIC TO GENERATE TRIGGER EVENT REPORTING DATAINDICATING THE DETECTED TRIGGER EVENT HAS BEEN DETECTED OPERATION 715 istransferred from the self-monitoring, self-reporting, and self-repairingvirtual asset to the virtual asset monitoring system of PROVIDE AVIRTUAL ASSET MONITORING SYSTEM OPERATION 703 using the virtual assetself-reporting communications channel generated by the virtual assetself-reporting communications channel creation logic at USE THESELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATE ASELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING,SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSETMONITORING SYSTEM OPERATION 717.

In one embodiment, once the detected trigger event data generated by thevirtual asset self-reporting logic at USE THE VIRTUAL ASSETSELF-REPORTING LOGIC TO GENERATE TRIGGER EVENT REPORTING DATA INDICATINGTHE DETECTED TRIGGER EVENT HAS BEEN DETECTED OPERATION 715 istransferred from the self-monitoring, self-reporting, and self-repairingvirtual asset to the virtual asset monitoring system of PROVIDE AVIRTUAL ASSET MONITORING SYSTEM OPERATION 703 using the virtual assetself-reporting communications channel generated by the virtual assetself-reporting communications channel creation logic at USE THESELF-REPORTING COMMUNICATIONS CHANNEL TO TRANSFER THE TRIGGER EVENTREPORTING DATA FROM THE SELF-MONITORING, SELF-REPORTING, ANDSELF-REPAIRING VIRTUAL ASSET TO THE VIRTUAL ASSET MONITORING SYSTEMOPERATION 719, process flow proceeds to GENERATE RESPONSIVE ACTIONIMPLEMENTATION DATA IMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THEDETECTED TRIGGER EVENT OPERATION 721.

In one embodiment, at GENERATE RESPONSIVE ACTION IMPLEMENTATION DATAIMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THE DETECTED TRIGGEREVENT OPERATION 721, analysis is performed at the virtual assetmonitoring system and the appropriate, or mapped, responsive actionimplementation data associated with the received trigger event data isidentified.

In one embodiment, the analysis performed at GENERATE RESPONSIVE ACTIONIMPLEMENTATION DATA IMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THEDETECTED TRIGGER EVENT OPERATION 721 includes mapping the detectedtrigger event data received to associated responsive actionimplementation data representing instructions for implementing one ormore responsive actions to the trigger event indicated in the triggerevent reporting data.

In various embodiments, the one or more responsive actions to thetrigger event indicated in the trigger event reporting data representedin the associated responsive action implementation data includes dataand instructions for, but not limited to, any of the followingoperations: ignoring the detected trigger event; requesting that thedetected trigger event data no longer be reported; performing one ormore scans on all, or part, of the logic and data contained and/orprocessed by the self-monitoring, self-reporting, and self-repairingvirtual assets, in one embodiment to attempt to identify malicious codeor activity; obtaining data from the self-monitoring, self-reporting,and self-repairing virtual assets; destroying data within theself-monitoring, self-reporting, and self-repairing virtual assets;directing a transfer of data from within the self-monitoring,self-reporting, and self-repairing virtual assets to a location outsidethe self-monitoring, self-reporting, and self-repairing virtual assets,e.g., pulling data from the self-monitoring, self-reporting, andself-repairing virtual assets prior to destroying the self-monitoring,self-reporting, and self-repairing virtual assets; closing down one ormore communications channels used by the self-monitoring,self-reporting, and self-repairing virtual assets; shutting down, oroff, one or more capabilities of the self-monitoring, self-reporting,and self-repairing virtual assets; aborting one or more operations beingperformed by the self-monitoring, self-reporting, and self-repairingvirtual assets; destroying the self-monitoring, self-reporting, andself-repairing virtual assets; and/or generating and/or transferringincorrect and/or deceptive data from the self-monitoring,self-reporting, and self-repairing virtual assets to a location outsidethe self-monitoring, self-reporting, and self-repairing virtual asset,such as a location or source associated with a malicious party; and/orany other desired responsive actions, or combination of responsiveactions, as discussed herein, and/or as known in the art at the time offiling, and/or as developed/become available after the time of filing.

In one embodiment, once analysis is performed at the virtual assetmonitoring system and the appropriate, or mapped, responsive actionimplementation data associated with the received trigger event data isidentified at GENERATE RESPONSIVE ACTION IMPLEMENTATION DATAIMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THE DETECTED TRIGGEREVENT OPERATION 721, process flow proceeds to TRANSFER THE RESPONSIVEACTION IMPLEMENTATION DATA FROM THE VIRTUAL ASSET MONITORING SYSTEM TOTHE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSETOPERATION 723.

In one embodiment, at TRANSFER THE RESPONSIVE ACTION IMPLEMENTATION DATAFROM THE VIRTUAL ASSET MONITORING SYSTEM TO THE SELF-MONITORING,SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET OPERATION 723, theappropriate, or mapped, responsive action implementation data associatedwith the received trigger event data of GENERATE RESPONSIVE ACTIONIMPLEMENTATION DATA IMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THEDETECTED TRIGGER EVENT OPERATION 721 is provided to the self-monitoring,self-reporting, and self-repairing virtual asset.

In one embodiment, at TRANSFER THE RESPONSIVE ACTION IMPLEMENTATION DATAFROM THE VIRTUAL ASSET MONITORING SYSTEM TO THE SELF-MONITORING,SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET OPERATION 723, theappropriate, or mapped, responsive action implementation data associatedwith the received trigger event data of GENERATE RESPONSIVE ACTIONIMPLEMENTATION DATA IMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THEDETECTED TRIGGER EVENT OPERATION 721 is provided to the self-monitoring,self-reporting, and self-repairing virtual asset using the virtual assetself-reporting communication channel, and the virtual assetself-reporting communications port, generated by the virtual assetself-reporting communications channel creation logic provided to theself-monitoring, self-reporting, and self-repairing virtual asset.

In one embodiment, once the appropriate, or mapped, responsive actionimplementation data associated with the received trigger event data ofGENERATE RESPONSIVE ACTION IMPLEMENTATION DATA IMPLEMENTING ONE OR MORERESPONSIVE ACTIONS TO THE DETECTED TRIGGER EVENT OPERATION 721 isprovided to the self-monitoring, self-reporting, and self-repairingvirtual asset at TRANSFER THE RESPONSIVE ACTION IMPLEMENTATION DATA FROMTHE VIRTUAL ASSET MONITORING SYSTEM TO THE SELF-MONITORING,SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET OPERATION 723, processflow proceeds to USE THE RESPONSIVE ACTION IMPLEMENTATION DATA TOIMPLEMENT THE ONE OR MORE RESPONSIVE ACTIONS TO THE TRIGGER EVENTINDICATED IN THE TRIGGER EVENT REPORTING DATA OPERATION 725.

In one embodiment, at USE THE RESPONSIVE ACTION IMPLEMENTATION DATA TOIMPLEMENT THE ONE OR MORE RESPONSIVE ACTIONS TO THE TRIGGER EVENTINDICATED IN THE TRIGGER EVENT REPORTING DATA OPERATION 725, theappropriate, or mapped, responsive action implementation data is used bythe self-monitoring, self-reporting, and self-repairing virtual asset toimplement the responsive action associated with the responsive actionimplementation data.

As noted above, in various embodiments the responsive actions associatedwith the responsive action implementation data implemented at USE THERESPONSIVE ACTION IMPLEMENTATION DATA TO IMPLEMENT THE ONE OR MORERESPONSIVE ACTIONS TO THE TRIGGER EVENT INDICATED IN THE TRIGGER EVENTREPORTING DATA OPERATION 725 can include, but are not limited to, anyone or more of, ignoring the detected trigger data; requesting thedetected trigger data no longer be sent; performing a scan of selecteddata within the self-monitoring, self-reporting, and self-repairingvirtual asset; obtaining data from the self-monitoring, self-reporting,and self-repairing virtual asset; directing a transfer of data fromwithin the self-monitoring, self-reporting, and self-repairing virtualasset to a location outside the self-monitoring, self-reporting, andself-repairing virtual asset; closing down one or more communicationschannels used by the self-monitoring, self-reporting, and self-repairingvirtual asset; shutting down one or more capabilities of theself-monitoring, self-reporting, and self-repairing virtual asset;aborting one or more operations performed by the self-monitoring,self-reporting, and self-repairing virtual asset; destroying theself-monitoring, self-reporting, and self-repairing virtual asset;generating and/or transferring incorrect and/or deceptive data from theself-monitoring, self-reporting, and self-repairing virtual asset to alocation outside the self-monitoring, self-reporting, and self-repairingvirtual asset associated with a malicious entity; and/or any otherdesired responsive actions, or combination of responsive actions, asdiscussed herein, and/or as known in the art at the time of filing,and/or as developed/become available after the time of filing.

In one embodiment, once the appropriate, or mapped, responsive actionimplementation data is used by the self-monitoring, self-reporting, andself-repairing virtual asset to implement the responsive actionassociated with the responsive action implementation data at USE THERESPONSIVE ACTION IMPLEMENTATION DATA TO IMPLEMENT THE ONE OR MORERESPONSIVE ACTIONS TO THE TRIGGER EVENT INDICATED IN THE TRIGGER EVENTREPORTING DATA OPERATION 725, process flow proceeds to EXIT OPERATION730.

In one embodiment, at EXIT OPERATION 730 process 700 for providingself-monitoring, self-reporting, and self-repairing virtual assets isexited to await new data.

In the discussion above, certain aspects of one embodiment includeprocess steps and/or operations and/or instructions described herein forillustrative purposes in a particular order and/or grouping. However,the particular order and/or grouping shown and discussed herein areillustrative only and not limiting. Those of skill in the art willrecognize that other orders and/or grouping of the process steps and/oroperations and/or instructions are possible and, in some embodiments,one or more of the process steps and/or operations and/or instructionsdiscussed above can be combined and/or deleted. In addition, portions ofone or more of the process steps and/or operations and/or instructionscan be re-grouped as portions of one or more other of the process stepsand/or operations and/or instructions discussed herein. Consequently,the particular order and/or grouping of the process steps and/oroperations and/or instructions discussed herein do not limit the scopeof the invention as claimed below.

As discussed in more detail above, using the above embodiments, withlittle or no modification and/or input, there is considerableflexibility, adaptability, and opportunity for customization to meet thespecific needs of various parties under numerous circumstances.

The present invention has been described in particular detail withrespect to specific possible embodiments. Those of skill in the art willappreciate that the invention may be practiced in other embodiments. Forexample, the nomenclature used for components, capitalization ofcomponent designations and terms, the attributes, data structures, orany other programming or structural aspect is not significant,mandatory, or limiting, and the mechanisms that implement the inventionor its features can have various different names, formats, or protocols.Further, the system or functionality of the invention may be implementedvia various combinations of software and hardware, as described, orentirely in hardware elements. Also, particular divisions offunctionality between the various components described herein are merelyexemplary, and not mandatory or significant. Consequently, functionsperformed by a single component may, in other embodiments, be performedby multiple components, and functions performed by multiple componentsmay, in other embodiments, be performed by a single component.

Some portions of the above description present the features of thepresent invention in terms of algorithms and symbolic representations ofoperations, or algorithm-like representations, of operations oninformation/data. These algorithmic or algorithm-like descriptions andrepresentations are the means used by those of skill in the art to mosteffectively and efficiently convey the substance of their work to othersof skill in the art. These operations, while described functionally orlogically, are understood to be implemented by computer programs orcomputing systems. Furthermore, it has also proven convenient at timesto refer to these arrangements of operations as steps or modules or byfunctional names, without loss of generality.

Unless specifically stated otherwise, as would be apparent from theabove discussion, it is appreciated that throughout the abovedescription, discussions utilizing terms such as, but not limited to,“activating,” “accessing,” “aggregating,” “alerting,” “applying,”“analyzing,” “associating,” “calculating,” “capturing,” “categorizing,”“classifying,” “comparing,” “creating,” “defining,” “detecting,”“determining,” “distributing,” “encrypting,” “extracting,” “filtering,”“forwarding,” “generating,” “identifying,” “implementing,” “informing,”“monitoring,” “obtaining,” “posting,” “processing,” “providing,”“receiving,” “requesting,” “saving,” “sending,” “storing,”“transferring,” “transforming,” “transmitting,” “using,” etc., refer tothe action and process of a computing system or similar electronicdevice that manipulates and operates on data represented as physical(electronic) quantities within the computing system memories, resisters,caches or other information storage, transmission or display devices.

The present invention also relates to an apparatus or system forperforming the operations described herein. This apparatus or system maybe specifically constructed for the required purposes, or the apparatusor system can comprise a general purpose system selectively activated orconfigured/reconfigured by a computer program stored on a computerprogram product as discussed herein that can be accessed by a computingsystem or other device.

Those of skill in the art will readily recognize that the algorithms andoperations presented herein are not inherently related to any particularcomputing system, computer architecture, computer or industry standard,or any other specific apparatus. Various general purpose systems mayalso be used with programs in accordance with the teaching herein, or itmay prove more convenient/efficient to construct more specializedapparatuses to perform the required operations described herein. Therequired structure for a variety of these systems will be apparent tothose of skill in the art, along with equivalent variations. Inaddition, the present invention is not described with reference to anyparticular programming language and it is appreciated that a variety ofprogramming languages may be used to implement the teachings of thepresent invention as described herein, and any references to a specificlanguage or languages are provided for illustrative purposes only.

The present invention is well suited to a wide variety of computernetwork systems operating over numerous topologies. Within this field,the configuration and management of large networks comprise storagedevices and computers that are communicatively coupled to similar ordissimilar computers and storage devices over a private network, a LAN,a WAN, a private network, or a public network, such as the Internet.

It should also be noted that the language used in the specification hasbeen principally selected for readability, clarity and instructionalpurposes, and may not have been selected to delineate or circumscribethe inventive subject matter. Accordingly, the disclosure of the presentinvention is intended to be illustrative, but not limiting, of the scopeof the invention, which is set forth in the claims below.

In addition, the operations shown in the figures, or as discussedherein, are identified using a particular nomenclature for ease ofdescription and understanding, but other nomenclature is often used inthe art to identify equivalent operations.

Therefore, numerous variations, whether explicitly provided for by thespecification or implied by the specification or not, may be implementedby one of skill in the art in view of this disclosure.

What is claimed is:
 1. A system comprising: one or more processors; andat least one memory coupled to the one or more processors, the at leastone memory having stored therein instructions which when executed by anyset of the one or more processors, perform a process including:providing a cloud computing environment, the cloud computing environmentincluding one or more virtual assets instantiated and executing withinthe cloud computing environment by a computing processor, the one ormore virtual assets comprising, at instantiation: virtual assetself-monitoring logic, the virtual asset self-monitoring logic includingdata and instructions for detecting one or more trigger events of thevirtual asset; virtual asset self-reporting logic, the virtual assetself-reporting logic including data and instructions for generatingtrigger event reporting data if one of the one or more trigger events isdetected in the virtual asset by the virtual asset self-monitoringlogic; self-reporting communications channel creation logic, theself-reporting communications channel creation logic including data andinstructions for opening a self-reporting communications channel betweenthe virtual asset and a virtual asset monitoring system responsive toone of the one or more trigger events being detected in the virtualasset by the virtual asset self-monitoring logic; and trigger eventreporting data transfer logic, the trigger event reporting data transferlogic including data and instructions for transferring the trigger eventreporting data from the virtual asset to the virtual asset monitoringsystem if one of the one or more trigger events is detected in thevirtual asset by the virtual asset self-monitoring logic; using thevirtual asset self-monitoring logic to monitor at least a portion ofmessage traffic sent to the virtual asset to detect any message meetingone or more trigger parameters; classifying one or more portions of thedetected at least one message as being suspect, the classified portionsof the detected message satisfying the one or more predefined triggerparameters; assigning a threat score to the suspect message at leastpartially based on a potential impact of the suspect message's potentialsecurity threat on the virtual asset; enabling, by providing the threatscore to the virtual asset, the extrusion detection capable virtualasset to secure against the suspect message; for each suspect message,generating suspect message copy data representing a copy of at least aportion of the suspect message; and transferring the suspect messagecopy data to one or more analysis systems for further analysis.
 2. Thesystem of claim 1 further comprising providing the virtual assets, atinstantiation: responsive action implementation data receipt logic, theresponsive action implementation data receipt logic including data andinstructions for receiving responsive action implementation data fromthe virtual asset monitoring system; and responsive actionimplementation logic, the responsive action implementation logicincluding data and instructions for implementing the one or moreresponsive actions indicated in the responsive action implementationdata received by the responsive action implementation data receiptlogic.
 3. The system claim 1 wherein at least one of the one or moretrigger events is selected from the group of trigger events consistingof: a network message from a virtual asset directed to a location knownto be associated with malicious entities; a frequency of outgoingnetwork messages changing level above a defined threshold level; aresponse to a customer request being directed to a destination that isnot the customer location of record; a virtual asset receiving ahigh-frequency of login attempts that fail; a size of the parameterssent into a virtual asset being outside a defined range; a size ofoutgoing network messages being outside a defined range; a total amountof data in any one communication connection of a virtual asset exceedinga defined maximum; a request to a virtual asset coming in from alocation known to be associated with malicious entities; and an internalelapsed time of defined critical operations changing to a time outside adefined range.
 4. The system of claim 1 wherein the suspect message copydata associated with a given suspect message is transferred to aspecific analysis system of the one or more analysis systems for furtheranalysis based, at least in part, on the specific trigger parameter ofthe one or more trigger parameters detected in the suspect message. 5.The system of claim 1 wherein if, as a result of the further analysis atthe one or more analysis systems, the suspect message is determined tobe an intrusion related message, one or more protective actions areautomatically implemented.
 6. The system of claim 1, wherein the virtualasset is a virtual asset selected from the group of the virtual assetsconsisting of: a virtual machine; a virtual server; a database or datastore; an instance in a cloud environment; a cloud environment accesssystem; part of a mobile device; part of a remote sensor; part of aserver computing system; and part of a desktop computing system.
 7. Thesystem of claim 1, wherein defining one or more trigger parametersincludes retrieving trigger parameters from an information managementsecurity vendor.
 8. The system of claim 1, wherein assigning the threatscore includes assigning a number of a predetermined range of numbers tothe suspect message, wherein a higher number is associated with a highersecurity priority.
 9. The system of claim 1, wherein providing thethreat score includes delaying transmission of the threat score based ona priority of the suspect message.
 10. The system of claim 1, whereinassigning the threat score to the suspect message includes evaluating aservice configuration to determine a vulnerability of the virtual asset.11. The system of claim 10, wherein the service configuration includeshardware characteristics of a host computing system of the virtualasset, and a type of information stored and provided by the virtualasset.
 12. A computing system implemented method, which when executed byone or more computing processors, performs process operationscomprising: providing a cloud computing environment, the cloud computingenvironment including one or more virtual assets instantiated within thecloud computing environment, the one or more virtual assets comprising,at instantiation: virtual asset self-monitoring logic including data andinstructions for detecting one or more trigger events of the virtualasset; virtual asset self-reporting logic including data andinstructions for generating trigger event reporting data if one of theone or more trigger events is detected in the virtual asset by thevirtual asset self-monitoring logic; self-reporting communicationschannel creation logic including data and instructions for opening aself-reporting communications channel between the virtual asset and avirtual asset monitoring system responsive to one of the one or moretrigger events being detected in the virtual asset by the virtual assetself-monitoring logic; and trigger event reporting data transfer logicincluding data and instructions for transferring the trigger eventreporting data from the virtual asset to the virtual asset monitoringsystem if one of the one or more trigger events is detected in thevirtual asset by the virtual asset self-monitoring logic; using thevirtual asset self-monitoring logic to monitor at least a portion ofmessage traffic sent to the virtual asset to detect any message meetingone or more trigger parameters; classifying one or more portions of adetected message as being suspect, the classified portions of thedetected message satisfying the one or more predefined triggerparameters; assigning a threat score to the suspect message at leastpartially based on a potential impact of the suspect message's potentialsecurity threat to the virtual asset; enabling, by providing the threatscore to the virtual asset, the virtual asset to secure against thesuspect message; for each suspect message, generating suspect messagecopy data representing a copy of at least a portion of the suspectmessage; and transferring the suspect message copy data to one or moreanalysis systems for further analysis.
 13. The computing systemimplemented method of claim 12 further comprising providing the virtualassets, at instantiation: responsive action implementation data receiptlogic, the responsive action implementation data receipt logic includingdata and instructions for receiving responsive action implementationdata from the virtual asset monitoring system; and responsive actionimplementation logic, the responsive action implementation logicincluding data and instructions for implementing the one or moreresponsive actions indicated in the responsive action implementationdata received by the responsive action implementation data receiptlogic.
 14. The computing system implemented method of claim 12 whereinat least one of the one or more trigger events is selected from thegroup of trigger events consisting of: a network message from a virtualasset directed to a location known to be associated with maliciousentities; a frequency of outgoing network messages changing level abovea defined threshold level; a response to a customer request beingdirected to a destination that is not the customer location of record; avirtual asset receiving a high-frequency of login attempts that fail; asize of the parameters sent into a virtual asset being outside a definedrange; a size of outgoing network messages being outside a definedrange; a total amount of data in any one communication connection of avirtual asset exceeding a defined maximum; a request to a virtual assetcoming in from a location known to be associated with maliciousentities; and an internal elapsed time of defined critical operationschanging to a time outside a defined range.
 15. The computing systemimplemented method of claim 12 wherein the suspect message copy dataassociated with a given suspect message is transferred to a specificanalysis system of the one or more analysis systems for further analysisbased, at least in part, on the specific trigger parameter of the one ormore trigger parameters detected in the suspect message.
 16. Thecomputing system implemented method of claim 12 wherein if, as a resultof the further analysis at the one or more analysis systems, the suspectmessage is determined to be an intrusion related message, one or moreprotective actions are automatically implemented.
 17. The computingsystem implemented method of claim 12, wherein the virtual asset is avirtual asset selected from the group of the virtual assets consistingof: a virtual machine; a virtual server; a database or data store; aninstance in a cloud environment; a cloud environment access system; partof a mobile device; part of a remote sensor; part of a server computingsystem; and part of a desktop computing system.
 18. The computing systemimplemented method of claim 12, wherein defining one or more triggerparameters includes retrieving trigger parameters from an informationmanagement security vendor.
 19. The computing system implemented methodof claim 12, wherein assigning the threat score includes assigning anumber of a predetermined range of numbers to the suspect message,wherein a higher number is associated with a higher security priority.20. The computing system implemented method of claim 12, whereinproviding the threat score includes delaying transmission of the threatscore based on a priority of the suspect message.
 21. The computingsystem implemented method of claim 12, wherein assigning the threatscore to the suspect message includes evaluating a service configurationto determine a vulnerability of the virtual asset.
 22. The computingsystem implemented method of claim 21, wherein the service configurationincludes hardware characteristics of a host computing system of thevirtual asset, and a type of information stored and provided by thevirtual asset.